Perma [tier 2] webgpu [taskcluster:error] exit status 2 when Gecko 113 merges to Beta on 2023-04-10
Categories
(Core :: Graphics: WebGPU, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr102 | --- | unaffected |
| firefox111 | --- | unaffected |
| firefox112 | --- | unaffected |
| firefox113 | + | fixed |
People
(Reporter: abutkovits, Assigned: jimb)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
[Tracking Requested - why for this release]:
|
Reporter | |
Updated•1 year ago
|
|
||
Comment 1•1 year ago
|
||
Conservatively marking as blocking webgpu-v1. If somebody knows better, feel free to correct.
|
||
Comment 2•1 year ago
|
||
:jimb, since you are the author of the regressor, bug 1824447, could you take a look?
For more information, please visit auto_nag documentation.
|
||
Comment 3•1 year ago
|
||
It looks like the issue may be that we're skipping all the tests in the suite, which ends up causing a failure for the run. If we're not interested in running debug-mochitest-webgpu on mingw builds, we should skip it at the TC level probably.
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
|
Assignee | |
Comment 6•1 year ago
|
||
(In reply to Ryan VanderMeulen [:RyanVM] from comment #3)
It looks like the issue may be that we're skipping all the tests in the suite, which ends up causing a failure for the run. If we're not interested in running debug-mochitest-webgpu on mingw builds, we should skip it at the TC level probably.
I don't know any reason webgpu shouldn't work in mingw builds, but we're not going to look into this problem in the near future. Skipping seems fine.
|
|
||
Comment 7•1 year ago
•
|
||
OK, the issue here isn't about mingw. This is a general issue with mochitest-webgpu and the run-if = !release_or_beta condition at the top of the mochitest manifest. The reason it's showing up in the uplift simulations is that mingw is the only platform that mochitest-webgpu runs on on Beta:
https://searchfox.org/mozilla-central/rev/8433b62e54fd30663e82f090c4d31554531a2e66/taskcluster/ci/test/mochitest.yml#973
So in general, I think we should rectify what we're telling TC to run vs. what we're telling the harness to run via the test manifest. Jim, can you please add some clarity to that? In general, maybe we should try to clean up the variant scheduling in that run-on-projects section.
|
|
Assignee | |
Comment 8•1 year ago
|
||
It seems like WebGPU was enabled on mingw in release by bug 1750398. There's no reason it should run there.
|
|
Assignee | |
Comment 9•1 year ago
|
||
At the moment, WebGPU is only enabled in nightly builds. Bug 1750398 accidentally enabled the WebGPU mochitests in all "release" builds, but that doesn't make sense yet.
|
||
Updated•1 year ago
|
|
||
Comment 10•1 year ago
|
||
Pushed by jblandy@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/635a498afc77 Only run WebGPU mochitests on mingw in mozilla-central. r=RyanVM
|
||
Comment 11•1 year ago
|
||
| bugherder | ||
| Comment hidden (Intermittent Failures Robot) |
Description
•