[wmfme] Perma dom/media/test/test_loop.html | single tracking bug
Categories
(Core :: Audio/Video: Playback, defect, P3)
Tracking
()
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)
Reporter | ||
Comment 1•3 years ago
|
||
Additional information about this bug failures and frequency patterns can be found by running: ./mach test-info failure-report --bug 1781539
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Comment hidden (Intermittent Failures Robot) |
![]() |
||
Updated•3 years ago
|
Comment 4•3 years ago
|
||
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?
Updated•3 years ago
|
Assignee | ||
Comment 5•3 years ago
|
||
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.
Assignee | ||
Comment 6•3 years ago
|
||
This is not permanent, I haven't been able to reproduce this on the try server yet.
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 9•3 years ago
•
|
||
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.
Assignee | ||
Comment 10•3 years ago
|
||
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.
Comment 11•3 years ago
|
||
Hi, we will ignore it until you can find a fix for it, thank for looking into this.
Comment hidden (Intermittent Failures Robot) |
Comment 13•3 years ago
|
||
Set release status flags based on info from the regressing bug 1790463
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Updated•3 years ago
|
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Updated•3 years ago
|
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Updated•3 years ago
|
Comment hidden (Intermittent Failures Robot) |
Updated•3 years ago
|
![]() |
||
Comment 24•3 years ago
|
||
Depends on D160691
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 28•3 years ago
|
||
Comment 29•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/c22ae0b1a20c
https://hg.mozilla.org/mozilla-central/rev/b114715a2220
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Description
•