Skip to content

ci: run GPU job on Mesa lavapipe instead of SwiftShader - #71

Closed
bhouston wants to merge 15 commits into
mainfrom
ci/70-gpu-lavapipe
Closed

bhouston wants to merge 15 commits into
mainfrom
ci/70-gpu-lavapipe

Conversation

@bhouston

@bhouston bhouston commented Nov 2, 2026

Copy link
Copy Markdown
Owner

Closes #70

Mirrors three.js e2e: mesa-vulkan-drivers + xvfb, VK_DRIVER_FILES=lvp ICD, headed Chromium under xvfb-run. Local behaviour unchanged. Adds a setup file logging GPUAdapter.info.

@codecov-commenter

Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@bhouston

bhouston commented Nov 6, 2026

Copy link
Copy Markdown
Owner Author

Closing: stock Chrome's WebGPU layer (Dawn) doesn't offer lavapipe. On Chrome for Testing 153 and stable Chrome 157 it lists only SwiftShader and ANGLE/llvmpipe (Compatibility Mode), so requestAdapter() returned SwiftShader across every flag and env combination tried. The GPU job is disabled on main (c00adf5) and CI doesn't need a GPU, so this change isn't needed. GPU tests run locally on real hardware.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ci: run GPU job on Mesa lavapipe instead of SwiftShader

2 participants