Intermittent browser/base/content/test/webrtc/browser_device_controls_menus.js | waiting for vsync to be disabled - timed out after 50 tries.
Categories
(Firefox :: Site Permissions, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr128 | --- | unaffected |
| firefox-esr140 | --- | unaffected |
| firefox141 | --- | unaffected |
| firefox142 | --- | unaffected |
| firefox143 | --- | fix-optional |
People
(Reporter: jib, Unassigned)
References
(Blocks 1 open bug, Regression)
Details
(4 keywords, Whiteboard: [stockwell disabled])
Attachments
(3 files)
https://treeherder.mozilla.org/intermittent-failures/bugdetails?startday=2025-07-05&endday=2025-08-04&tree=all&failurehash=all&bug=1775940 spiked a day after bug 799415 landed. Coincidence?
Not a lot to go on here, as these tests have been subject to a lot of intermittents over the years tracked in bug 1775940 and bugs filed for related tests in the same toml, but wanted to file this data point.
According to the failure logs the test is trying to disable vsync and failing to do so.
From the logs: vsync remained enabled at the end of the test. Is there an animation still running? Consider talking to the performance team for tips to solve this. - false == true
Comment 1•5 months ago
|
||
Set release status flags based on info from the regressing bug 799415
:emz, since you are the author of the regressor, bug 799415, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Updated•5 months ago
|
Comment 2•4 months ago
|
||
(In reply to Jan-Ivar Bruaroey [:jib] (needinfo? me) from comment #0)
According to the failure logs the test is trying to disable vsync and failing to do so.
All browser chrome mochitests way for vsync to be disabled (ie no visual update is pending anymore) before moving on to the next test. If vsync is still not disabled 5s after a test finished, a failure is reported.
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Comment 13•2 months ago
|
||
Comment 14•2 months ago
|
||
Updated•2 months ago
|
Comment 15•2 months ago
|
||
| bugherder | ||
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 18•2 months ago
|
||
Comment 19•2 months ago
|
||
Comment 20•2 months ago
|
||
| bugherder | ||
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Updated•2 days ago
|
Comment 24•2 days ago
|
||
We should check if the fix for Bug 2007284 also fixes this issue. I'll add re-enabling the tests as a separate patch to the stack.
Description
•