Run WebGPU browser tests in CI - #706
Draft
ibgreen wants to merge 3 commits into
Draft
Conversation
CoverageStmts: 51.01% ▼-0.01% | Branch: 42.11% | Funcs: 49.15% | Lines: 51.12% ▼-0.01%
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/whats-new.mdThis draft is intentionally independent of #705 and targets
masterdirectly. The WebGPU layer-port PR does not depend on this branch and can land separately.Current status
Local software-WebGPU validation passes, but GitHub's Ubuntu runner still fails the headless job: the first native WebGPU rendering file loses Dawn's external instance, followed by six failures across five WebGPU browser files.
The failure persists with browser files serialized, explicit WebGPU-device teardown removed, and Chromium's documented
--use-webgpu-adapter=swiftshader/--use-gpu-in-testsconfiguration. This draft therefore remains an isolated CI investigation; it is not ready to land and does not block #705.Chromium reference:
webgpu-swiftshaderflag configuration.Likely next steps are to capture
chrome://gpuand adapter diagnostics on the runner, then determine whether the hosted Chrome/Dawn build needs a different Linux image, Vulkan setup, or dedicated GPU-capable runner.Validation
yarn lintyarn test: 168 files passed; 1,420 tests passed, 9 skippedGITHUB_ACTIONS=true DECK_GL_COMMUNITY_SOFTWARE_WEBGPU=true yarn test-headless: 56 files passed; 438 tests passed, 0 skippedtest-headless: 432 passed, 6 failed across five WebGPU files