Closed Bug 1770556 Opened 3 years ago Closed 3 years ago

Intermittent browser/base/content/test/fullscreen/browser_fullscreen_window_focus.js | Test timed out - | Uncaught exception received from previously timed out test - focus listener not removed before the end of test

Categories

(Firefox :: General, defect, P5)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1775999

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [retriggered])

Filed by: imoraru [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=378847658&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Cr19L4yQSS6UJfIcpsEPwA/runs/0/artifacts/public/logs/live_backing.log


[task 2022-05-21T07:35:10.573Z] 07:35:10     INFO - TEST-START | browser/base/content/test/fullscreen/browser_fullscreen_window_focus.js
[task 2022-05-21T07:35:11.044Z] 07:35:11     INFO - GECKO(4196) | 1653118511058	Marionette	TRACE	Received observer notification browser-delayed-startup-finished
[task 2022-05-21T07:35:55.581Z] 07:35:55     INFO - TEST-INFO | started process screenshot
[task 2022-05-21T07:35:55.657Z] 07:35:55     INFO - TEST-INFO | screenshot: exit 0
[task 2022-05-21T07:35:55.668Z] 07:35:55     INFO - Buffered messages logged at 07:35:10
[task 2022-05-21T07:35:55.668Z] 07:35:55     INFO - Entering setup bound 
[task 2022-05-21T07:35:55.669Z] 07:35:55     INFO - Leaving setup bound 
[task 2022-05-21T07:35:55.669Z] 07:35:55     INFO - Entering test bound test_popupWindowFocus
[task 2022-05-21T07:35:55.670Z] 07:35:55     INFO - Calling window.open()
[task 2022-05-21T07:35:55.670Z] 07:35:55     INFO - Buffered messages finished
[task 2022-05-21T07:35:55.670Z] 07:35:55     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/fullscreen/browser_fullscreen_window_focus.js | Test timed out - 
[task 2022-05-21T07:35:55.671Z] 07:35:55     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-05-21T07:35:55.671Z] 07:35:55     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/fullscreen/browser_fullscreen_window_focus.js | Uncaught exception received from previously timed out test - focus listener not removed before the end of test
[task 2022-05-21T07:35:55.672Z] 07:35:55     INFO - Entering test bound test_iframePopupWindowFocus
[task 2022-05-21T07:35:55.672Z] 07:35:55     INFO - GECKO(4196) | MEMORY STAT | vsize 2104193MB | vsizeMaxContiguous 74417874MB | residentFast 232MB | heapAllocated 91MB
[task 2022-05-21T07:35:55.673Z] 07:35:55     INFO - TEST-OK | browser/base/content/test/fullscreen/browser_fullscreen_window_focus.js | took 45036ms
[task 2022-05-21T07:35:55.673Z] 07:35:55     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-05-21T07:35:55.674Z] 07:35:55     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/fullscreen/browser_fullscreen_window_focus.js | Found a tab after previous test timed out: about:blank - 
[task 2022-05-21T07:35:55.674Z] 07:35:55     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-05-21T07:35:55.677Z] 07:35:55     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/fullscreen/browser_fullscreen_window_focus.js | Found a tab after previous test timed out: https://example.com/browser/browser/base/content/test/fullscreen/open_and_focus_helper.html - 
[task 2022-05-21T07:35:55.677Z] 07:35:55     INFO - checking window state
[task 2022-05-21T07:35:55.677Z] 07:35:55     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-05-21T07:35:55.678Z] 07:35:55     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/fullscreen/browser_fullscreen_window_focus.js | Found a browser window after previous test timed out - 
[task 2022-05-21T07:35:55.678Z] 07:35:55     INFO - TEST-START | browser/base/content/test/fullscreen/browser_fullscreen_window_open.js

Could Bug 1769939 have anything to do with these failures? Retriggers here.

Flags: needinfo?(tnikkel)

There's failures in the past revisions, just seemed like less often. I retriggered a bunch of times on my push. No new failures, so I think my push just got unlucky? I wouldn't think there is any connection between my patch and those tests. If my patch did indeed change the frequency then my first thought would be that the test was already flakey and my patch just changed the timing slightly to make it fail more often.

I just did 8 (types of jobs) * 20 (retriggers) * 7 (different tips) = 1120 runs of the browserchrome chunk that has this test on try.
3 failures on tip with bug 1769939 backed out.
9 failures on tip.
1 failure on 4b4bd8a70d278e4f03be15d2e09ee3eb1c5d9a09 (landing of bug 1769939)
12 failures on a30460ae6d16a1e39e3b2140beb6d55396ca5ed2 (immediately before bug 1769939)
1 failure on ba3358377008ecb0b10cd3de8e3c6f2951663162 (further before)
2 failures on 2c5c5c7db243f26b0820005eae9dc11ca78aa849 (further before)
5 failures on 1d31a009897964e94d43db5961ff68538d5e8ddb (further before)

So it does not seem like bug 1769939 is involved. It seems like it varies randomly or due to some other condition perhaps related to the infrastructure or just randomness.

Flags: needinfo?(tnikkel)
Whiteboard: [retriggered]
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.