Closed Bug 1783214 Opened 2 years ago Closed 2 years ago

Intermittent browser/base/content/test/general/browser_beforeunload_duplicate_dialogs.js | single tracking bug

Categories

(Firefox :: General, defect, P5)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure, intermittent-testcase)

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


[task 2022-08-04T13:03:36.238Z] 13:03:36     INFO - TEST-PASS | browser/base/content/test/general/browser_beforeunload_duplicate_dialogs.js | Window should be closed. - 
[task 2022-08-04T13:03:36.239Z] 13:03:36     INFO - Leaving test bound closeWindoWithSingleTabTwice
[task 2022-08-04T13:03:36.239Z] 13:03:36     INFO - Buffered messages finished
[task 2022-08-04T13:03:36.240Z] 13:03:36     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/general/browser_beforeunload_duplicate_dialogs.js | waiting for vsync to be disabled - timed out after 50 tries. - false == true - JS frame :: chrome://mochikit/content/browser-test.js :: ensureVsyncDisabled :: line 575
[task 2022-08-04T13:03:36.240Z] 13:03:36     INFO - Stack trace:
[task 2022-08-04T13:03:36.240Z] 13:03:36     INFO - chrome://mochikit/content/browser-test.js:ensureVsyncDisabled:575
[task 2022-08-04T13:03:36.240Z] 13:03:36     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-08-04T13:03:36.241Z] 13:03:36     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/general/browser_beforeunload_duplicate_dialogs.js | 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 - JS frame :: chrome://mochikit/content/browser-test.js :: ensureVsyncDisabled :: line 576
[task 2022-08-04T13:03:36.241Z] 13:03:36     INFO - Stack trace:
[task 2022-08-04T13:03:36.241Z] 13:03:36     INFO - chrome://mochikit/content/browser-test.js:ensureVsyncDisabled:576
[task 2022-08-04T13:03:36.242Z] 13:03:36     INFO - GECKO(1470) | MEMORY STAT | vsize 16256MB | residentFast 361MB | heapAllocated 126MB
[task 2022-08-04T13:03:36.242Z] 13:03:36     INFO - TEST-OK | browser/base/content/test/general/browser_beforeunload_duplicate_dialogs.js | took 10254ms
[task 2022-08-04T13:03:36.242Z] 13:03:36     INFO - checking window state
[task 2022-08-04T13:03:36.243Z] 13:03:36     INFO - TEST-START | browser/base/content/test/general/browser_bug1261299.js

Hi Florian, could this be a regression of bug 1742842?

Flags: needinfo?(florian)

(In reply to Andreea Pavel [:apavel] from comment #1)

Hi Florian, could this be a regression of bug 1742842?

It's an existing issue that has been exposed by bug 1742842. We started investigating a bit in bug 1765387, and I landed a workaround with bug 1742842 with the setTimeout at: https://searchfox.org/mozilla-central/rev/5644fae86d5122519a0e34ee03117c88c6ed9b47/browser/base/content/test/general/browser_beforeunload_duplicate_dialogs.js#43,45 If the failure keeps happening or has a high frequency, maybe we should use a longer timeout (eg. 500ms instead of 375).

Flags: needinfo?(florian)
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Status: REOPENED → RESOLVED
Closed: 2 years ago2 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Status: REOPENED → RESOLVED
Closed: 2 years ago2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.