Repository navigation
[Impeller] Set up a CI shard focused on vulkan sync validation #195502
Description
When we fix individual Vulkan sync hazards like those in #194987, we can regression test them with a unit test operating on mocks. But this doesn't discover new sync hazards. Enabling sync validation adds a lot of CPU cost, so I don't recommend we run our whole suite of engine tests with it enabled. Instead, I recommend we set up a new CI shard with vulkan sync validation enabled (VK_VALIDATION_VALIDATE_SYNC=1 or VK_VALIDATION_FEATURE_ENABLE_SYNCHRONIZATION_VALIDATION_EXT) which covers a carefully selected set of impeller tests.
Reacted by gaaclarke
Activity
Adds Vulkan sync validation test run (flutter#195596)
[Impeller] Order the Vulkan copy-texture-to-texture layout transition…
Adds Vulkan sync validation test run (flutter#195596)
[Impeller] Order the Vulkan copy-texture-to-texture layout transition…
github-actions commentedon Nov 13, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.