-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
layers: Validate binary sync depenency on timeline wait #8739
base: main
Are you sure you want to change the base?
Conversation
This validates "and any semaphore signal operations on which it depends must have also been submitted for execution" from these VUIDs: VUID-vkQueueSubmit-pWaitSemaphores-03238 VUID-vkQueueSubmit2-semaphore-03873 VUID-vkQueuePresentKHR-pWaitSemaphores-03268 VUID-VkSemaphoreGetFdInfoKHR-handleType-03254
CI Vulkan-ValidationLayers build queued with queue ID 284488. |
CI Vulkan-ValidationLayers build # 17799 running. |
61052b8
to
2d389ad
Compare
CI Vulkan-ValidationLayers build queued with queue ID 284550. |
CI Vulkan-ValidationLayers build # 17800 running. |
CI Vulkan-ValidationLayers build # 17800 aborted. |
CI Vulkan-ValidationLayers build queued with queue ID 284712. |
CI Vulkan-ValidationLayers build # 17805 running. |
CI Vulkan-ValidationLayers build # 17805 failed. |
This partiallyaddresses #8707What's left for other PRs:
VUID-vkQueueSubmit-pWaitSemaphores-03238
: either missing binary signal or binary signal exists but depends on timeline wait.Try to analyze entire synchronization chain, not only direct parent.- actually this works, added one more test to show thisNegativeSyncObject.BinarySyncDependsOnTimelineWait3
.