-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Fix synchronization validation error in water example on Vulkan #5231
Copy link
Copy link
Open
Labels
area: correctnessWe're behaving incorrectlyWe're behaving incorrectlybackend: vulkanIssues with VulkanIssues with Vulkanhelp requiredWe need community help to make this happen.We need community help to make this happen.type: bugSomething isn't workingSomething isn't working
Description
GPU-based validation was implemented for the Vulkan backend in #5046 (🎉). With it, we began to run into a validation error for the water example:
[2024-02-02T20:25:58Z ERROR wgpu_test::expectations] Validation Error: Validation Error: [ SYNC-HAZARD-WRITE-AFTER-READ ] Object 0: handle = 0xa808d50000000033, type = VK_OBJECT_TYPE_RENDER_PASS; | MessageID = 0x376bc9df | vkCmdEndRenderPass: Hazard WRITE_AFTER_READ in subpass 0 for attachment 1 depth aspect during store with storeOp VK_ATTACHMENT_STORE_OP_STORE. Access info (usage: SYNC_LATE_FRAGMENT_TESTS_DEPTH_STENCIL_ATTACHMENT_WRITE, prior_usage: SYNC_FRAGMENT_SHADER_SHADER_SAMPLED_READ, read_barriers: VkPipelineStageFlags2(0), command: vkCmdDraw, seq_no: 2, reset_no: 1)
Because of the value of validation, that PR was merged without a complete fix to water, changing the outcome we expect of CI testing to failure. We should fix it, and adjust the expected test outcome of that example back to fully passing.
Additional historical context: #5046 (comment)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area: correctnessWe're behaving incorrectlyWe're behaving incorrectlybackend: vulkanIssues with VulkanIssues with Vulkanhelp requiredWe need community help to make this happen.We need community help to make this happen.type: bugSomething isn't workingSomething isn't working
Type
Projects
Status
Todo