Skip to content

Disable WebGPU for Firefox tests - #21364

Merged
timvandermeij merged 1 commit into
mozilla:masterfrom
timvandermeij:webgpu-logs
May 31, 2026
Merged

timvandermeij merged 1 commit into
mozilla:masterfrom
timvandermeij:webgpu-logs

Conversation

@timvandermeij

Copy link
Copy Markdown
Collaborator

The GitHub Actions workflow for the integration tests on Windows logs the following line for every test:

JavaScript warning: http://127.0.0.1:62313/build/generic/build/pdf.mjs, line 134934: WebGPU is disabled by blocklist.

On Linux WebGPU is disabled by default because of missing support, but on Windows it's enabled by default since bug 1972486, so we try to obtain a GPU adapter which fails (and logs) if there is no actual GPU like on GitHub Actions. Coverage data confirms that our own WebGPU code is already uncovered because of the lack of a GPU, so having WebGPU enabled or disabled doesn't change that, but if it causes log spam it seems better to disable it, which this commit does.

Note that Chrome doesn't seem to have a matching flag, but Chrome already doesn't log anything about this (which is the primary driver for this change), so that's not a problem.

The GitHub Actions workflow for the integration tests on Windows logs
the following line for every test:

`JavaScript warning: http://127.0.0.1:62313/build/generic/build/pdf.mjs,
line 134934: WebGPU is disabled by blocklist.`

On Linux WebGPU is disabled by default because of missing support, but on
Windows it's enabled by default since bug 1972486, so we try to obtain a
GPU adapter which fails (and logs) if there is no actual GPU like on
GitHub Actions. Coverage data confirms that our own WebGPU code is
already uncovered because of the lack of a GPU, so having WebGPU enabled
or disabled doesn't change that, but if it causes log spam it seems
better to disable it, which this commit does.

Note that Chrome doesn't seem to have a matching flag, but Chrome already
doesn't log anything about this (which is the primary driver for this
change), so that's not a problem.
@codecov-commenter

codecov-commenter commented May 30, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.45%. Comparing base (145feea) to head (eef4ea6).

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #21364      +/-   ##
==========================================
- Coverage   81.45%   81.45%   -0.01%     
==========================================
  Files         260      260              
  Lines       65817    65817              
==========================================
- Hits        53611    53608       -3     
- Misses      12206    12209       +3     
Flag Coverage Δ
fonttest 9.01% <ø> (ø)
integrationtest 66.71% <ø> (+<0.01%) ⬆️
unittest 57.03% <ø> (-0.02%) ⬇️
unittestcli 56.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@timvandermeij
timvandermeij requested a review from calixteman May 30, 2026 17:36

@calixteman calixteman left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thank you<

@timvandermeij
timvandermeij merged commit af23800 into mozilla:master May 31, 2026
22 checks passed
@timvandermeij
timvandermeij deleted the webgpu-logs branch May 31, 2026 09:19

This branch was previously deployed

1 inactive deployment
code-coverage — eef4ea62 Deployed May 30, 2026 by timvandermeij via windows-latest / chrome #586
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants