Closed Bug 1914635 Opened 2 months ago Closed 1 month ago

Intermittent dom/webgpu/mochitest/test_disabled.html | single tracking bug

Categories

(Core :: Graphics: WebGPU, defect, P5)

defect

Tracking

()

RESOLVED FIXED
132 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- unaffected
firefox129 --- unaffected
firefox130 --- unaffected
firefox131 --- wontfix
firefox132 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: jmaher)

References

(Regression)

Details

(Keywords: intermittent-testcase, regression)

Attachments

(1 file)

Depends on: 1913649
Summary: Perma dom/webgpu/mochitest/test_disabled.html in Try pushes | single tracking bug → Intermittent dom/webgpu/mochitest/test_disabled.html in Try pushes | single tracking bug

This seems to only affect Try pushes, and on a permanent basis. 🤔

Summary: Intermittent dom/webgpu/mochitest/test_disabled.html in Try pushes | single tracking bug → Intermittent dom/webgpu/mochitest/test_disabled.html | single tracking bug

It's only supposed to run for release or beta, the pushers here likely requests all mochitests or all webgpu tasks.

:aryx: As the person making the task requests, that hypothesis would make sense, except that I'm using essentially the same mochitest job requests as when things stopped working around August 10th (my last working push from then is at try:801b8bae0c96), after these tasks had otherwise worked since at least September of 2022. So, I'm stumped; I expect that to not matter, and for the Mochitest runner to filter out those tests based on the environment that the test is being run in.

I had made some changes on the extra-options field for mochitest-webgpu on August 2nd, and I'm investigating whether that's related with try:04f760673974. Does that sound like it might be relevant, :aryx?

Flags: needinfo?(aryx.bugmail)
Assignee: nobody → jmaher
Status: NEW → ASSIGNED

Set release status flags based on info from the regressing bug 1909512

Pushed by jmaher@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1223202d0f1c define release_or_beta properly when decision task picks manifests. r=aryx,taskgraph-reviewers,ahal
Status: ASSIGNED → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 132 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: