You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The wgpu sources have various comments here and there remarking on how lavapipe doesn't implement Vulkan well enough to fully support WebGPU, but I wonder if that's true any more. Apparently Linux Mesa lavapipe 22.1.2 passes the Vulkan 1.3 CTS.
We should go through wgpu and see what works now and which caveats still apply. It would sure be nice to have lavapipe for software-based testing.
The text was updated successfully, but these errors were encountered:
The zero_init_workgroup_mem test failing in CI (running via swiftshader currently) is becoming more and more prevalent. I wonder how lavapipe compares.
The zero_init_workgroup_mem test failing in CI is our fault not swiftshader's, it's the same thing affecting WARP: #3193
This wasn't obvious before as the vulkan validation layers were off. Afaict, there have been no spurious failures from swiftshader (that weren't our fault), but there have been quite a few from lavapipe. We should definitely try it again, but I have a lot more confidence in swiftshader than lavapipe.
The wgpu sources have various comments here and there remarking on how lavapipe doesn't implement Vulkan well enough to fully support WebGPU, but I wonder if that's true any more. Apparently Linux Mesa lavapipe 22.1.2 passes the Vulkan 1.3 CTS.
We should go through wgpu and see what works now and which caveats still apply. It would sure be nice to have lavapipe for software-based testing.
The text was updated successfully, but these errors were encountered: