Closed Bug 1781539 Opened 3 years ago Closed 3 years ago

[wmfme] Perma dom/media/test/test_loop.html | single tracking bug

Categories

(Core :: Audio/Video: Playback, defect, P3)

defect

Tracking

()

RESOLVED FIXED
108 Branch
Tracking Status
firefox-esr102 --- unaffected
firefox106 --- unaffected
firefox107 --- wontfix
firefox108 --- fixed

People

(Reporter: jmaher, Assigned: alwu)

References

(Regression)

Details

(Keywords: intermittent-failure, intermittent-testcase, regression, Whiteboard: [stockwell disable-recommended])

Attachments

(2 files)

No description provided.

Additional information about this bug failures and frequency patterns can be found by running: ./mach test-info failure-report --bug 1781539

Severity: normal → S3
Assignee: nobody → alwu
Blocks: 1781735
Summary: Intermittent dom/media/test/test_loop.html | single tracking bug → [wmfme] Intermittent dom/media/test/test_loop.html | single tracking bug
Summary: [wmfme] Intermittent dom/media/test/test_loop.html | single tracking bug → [wmfme] Permanent dom/media/test/test_loop.html | single tracking bug

This started to almost perma fail on Windows 10 x64 2004 WebRender opt
There are 57 failures in the last 2 days.
:alwu , can you please take a look?

Flags: needinfo?(alwu)
Regressed by: 1790463

Yes, that is something already in my radar. All failures are mochitest-media-wmfme which is a new tier 2 test task, the failure won't affect other test tasks on the try server.

Flags: needinfo?(alwu)

This is not permanent, I haven't been able to reproduce this on the try server yet.

Summary: [wmfme] Permanent dom/media/test/test_loop.html | single tracking bug → [wmfme] dom/media/test/test_loop.html | single tracking bug

Hello, this is mostly perma-failing on central and autoland (e.g. on central) (since they are configured the same), it could be that try is not catching this failure and that is why it's appearing on the other 2 trees only. Will change the summary back to perma for the time being.

Flags: needinfo?(alwu)
Summary: [wmfme] dom/media/test/test_loop.html | single tracking bug → [wmfme] Perma dom/media/test/test_loop.html | single tracking bug

Okay good to know that the failure rate is different between the try server and the central/autoland.

Could we simply ignore this test failure (and any test failures happening on wmfme) and keep the test in the tree, instead of disabling the test? Because wmfme is a tier 2 test task for the new feature which hasn't been enabled yet, so we need to track those failures and fix them one by one until the feature becomes stable. Then we would make wmfme be a tier 1 task, which means any test failures would be treated in the same guideline.

Thanks.

Flags: needinfo?(alwu) → needinfo?(nfay)

Hi, we will ignore it until you can find a fix for it, thank for looking into this.

Flags: needinfo?(nfay)

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

Whiteboard: [stockwell disable-recommended] → [stockwell needswork:owner]
Whiteboard: [stockwell disable-recommended] → [stockwell needswork:owner]
Whiteboard: [stockwell disable-recommended] → [stockwell needswork:owner]
Pushed by csabou@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c22ae0b1a20c add toggle 'wmfme' to mochitest runner to skip tests executed with this variant. r=jmaher https://hg.mozilla.org/integration/autoland/rev/b114715a2220 disable dom/media/test/test_loop.html in windows media foundation variant. r=alwu
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 108 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: