Closed Bug 1511706 Opened 6 years ago Closed 4 years ago

Intermittent dom/base/test/browser_bug1058164.js | Test timed out -

Categories

(Core :: DOM: Core & HTML, defect, P5)

defect

Tracking

()

RESOLVED FIXED
86 Branch
Tracking Status
firefox86 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: emilio)

Details

(Keywords: intermittent-failure)

Attachments

(1 file, 1 obsolete file)

Filed by: aciure [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=215160584&repo=mozilla-central https://queue.taskcluster.net/v1/task/eNfxXSWISGyeXL1ABkTqPQ/runs/0/artifacts/public/logs/live_backing.log 11:37:42 INFO - TEST-PASS | dom/base/test/browser_bug1058164.js | Got expected event - 11:37:42 INFO - waiting for hidden emptyBrowser to pageshow 11:37:42 INFO - Buffered messages finished 11:37:42 INFO - TEST-UNEXPECTED-FAIL | dom/base/test/browser_bug1058164.js | Test timed out - 11:37:42 INFO - GECKO(1292) | MEMORY STAT | vsize 727MB | vsizeMaxContiguous 732MB | residentFast 228MB | heapAllocated 88MB 11:37:42 INFO - TEST-OK | dom/base/test/browser_bug1058164.js | took 45035ms 11:37:42 INFO - Not taking screenshot here: see the one that was previously logged 11:37:42 INFO - TEST-UNEXPECTED-FAIL | dom/base/test/browser_bug1058164.js | Found a tab after previous test timed out: about:blank - 11:37:42 INFO - checking window state 11:37:42 INFO - Not taking screenshot here: see the one that was previously logged 11:37:42 INFO - TEST-UNEXPECTED-FAIL | dom/base/test/browser_bug1058164.js | Found a browser window after previous test timed out - 11:37:42 INFO - GECKO(1292) | must wait for focus
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Component: DOM → DOM: Core & HTML
Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Status: REOPENED → RESOLVED
Closed: 6 years ago5 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Status: REOPENED → RESOLVED
Closed: 5 years ago5 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Status: REOPENED → RESOLVED
Closed: 5 years ago5 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Status: REOPENED → RESOLVED
Closed: 5 years ago4 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Status: REOPENED → RESOLVED
Closed: 4 years ago4 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Status: REOPENED → RESOLVED
Closed: 4 years ago4 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---

The visibilityState being hidden doesn't necessarily mean that pageshow
hasn't run, it might also mean that the browser is not yet active, so
the test is racy. If the browser becomes active before pageshow runs,
then this code works as intended, but if pageshow has already fired but
the browser is not yet active, then the activeness change will fire a
visibilitychange event, but not a pageshow, and the document will become
visible but the test won't continue.

This race will become more frequent with D42329. Since we know that
pageshow has to have fired once the visibilityState is visible, wait for
that.

Assignee: nobody → emilio
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/64fcfd386e92 Fix waiting condition in browser_bug1058164.js. r=nika
Attached file Bug 1511706 - eslint fix. (obsolete) —
Attachment #9198501 - Attachment is obsolete: true
Status: REOPENED → RESOLVED
Closed: 4 years ago4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 86 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: