Perma [tier2] dom/base/test/fullscreen/test_fullscreen-api.html | Test timed out
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
People
(Reporter: intermittent-bug-filer, Assigned: bradwerth)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: intermittent-failure, intermittent-testcase, regression, Whiteboard: [stockwell needswork:owner])
Attachments
(1 obsolete file)
Filed by: chorotan [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=412981460&repo=mozilla-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/TinlUCH-QGmYoccW9eQGHA/runs/0/artifacts/public/logs/live_backing.log
task 2023-04-19T10:09:58.476Z] 10:09:58 INFO - TEST-PASS | dom/base/test/fullscreen/test_fullscreen-api.html | reftest comparison: == snapshot green
[task 2023-04-19T10:09:58.476Z] 10:09:58 INFO - Waiting for focus to return to main window
[task 2023-04-19T10:09:58.477Z] 10:09:58 INFO - testWindow.close()
[task 2023-04-19T10:09:58.478Z] 10:09:58 INFO - main window focused, starting next test
[task 2023-04-19T10:09:58.478Z] 10:09:58 INFO - Run test file_fullscreen-resize.html
[task 2023-04-19T10:09:58.479Z] 10:09:58 INFO - Buffered messages logged at 10:05:27
[task 2023-04-19T10:09:58.479Z] 10:09:58 INFO - Were focused
[task 2023-04-19T10:09:58.480Z] 10:09:58 INFO - [resize] Entered fullscreen
[task 2023-04-19T10:09:58.481Z] 10:09:58 INFO - Buffered messages finished
[task 2023-04-19T10:09:58.482Z] 10:09:58 INFO - TEST-UNEXPECTED-FAIL | dom/base/test/fullscreen/test_fullscreen-api.html | Test timed out. -
[task 2023-04-19T10:09:59.215Z] 10:09:59 INFO - GECKO(1580) | MEMORY STAT | vsize 2696MB | residentFast 161MB | heapAllocated 8MB
[task 2023-04-19T10:09:59.493Z] 10:09:59 INFO - TEST-OK | dom/base/test/fullscreen/test_fullscreen-api.html | took 314900ms
[task 2023-04-19T10:10:02.505Z] 10:10:02 INFO - Error: Unable to restore focus, expect failures and timeouts.
Updated•2 years ago
|
Comment 1•2 years ago
|
||
Brad, could your push cause this failure? It is perma failing only on central.
Assignee | ||
Comment 2•2 years ago
|
||
(In reply to Cristina Horotan [:chorotan] from comment #1)
Brad, could your push cause this failure? It is perma failing only on central.
Yes, that's very likely. Didn't see it in my try runs but I'll keep working on the patch stack in Bug 1826645 until I'm sure it's passing. Feel free to backout the changes.
Assignee | ||
Comment 3•2 years ago
|
||
(In reply to Brad Werth [:bradwerth] from comment #2)
Yes, that's very likely. Didn't see it in my try runs but I'll keep working on the patch stack in Bug 1826645 until I'm sure it's passing. Feel free to backout the changes.
Or since this is Tier 2, don't backout the changes and I'll build the fix here.
Assignee | ||
Comment 4•2 years ago
|
||
The failure is that we're bailing out of an exit fullscreen because of events/requests arriving in an unexpected order. This is what Bug 1826645 was trying to address, but we evidently have another mode of error. I'll find a fix.
Assignee | ||
Comment 5•2 years ago
|
||
I can get the file_fullscreen-resize.html
part of the test to fail locally on macOS while running in headless mode. I'll see if I can make the test pass in these circumstances.
Comment hidden (Intermittent Failures Robot) |
Comment 7•2 years ago
|
||
Since the test fails on headless widget only, maybe somehow headless widget behave different than other platforms (?), if that is the case, we could also consider making headless widget behave the same as other platforms if possible.
Assignee | ||
Comment 8•2 years ago
|
||
NSGlobalWindowOuter is the listener to HeadlessWidget. It maintains
internal fullscreen state which is checked in FinishFullscreenChange. It
is necessary for the widget to first call FullscreenWillChange in order to
have expected state before the call to FinishFullscreenChange.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 9•2 years ago
|
||
The fix for this issue will depend largely on Bug 1823284. If that Bug removes the FullscreenWillChange
listener method, then this Bug will need some other kind of fix to maintain the internal state in NSGlobalWindowOuter
.
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Bug 1823284 should also fix this.
Assignee | ||
Comment 14•1 year ago
|
||
Indeed, fixed by the patches in Bug 1823284.
Updated•1 year ago
|
Description
•