Closed Bug 1431154 Opened 8 years ago Closed 7 years ago

Intermittent browser/tools/mozscreenshots/primaryUI/browser_primaryUI.js | Unexpected exception in [ tabsInTitlebar, fiveTabs, maximized, onlyNavBar, noLWT, compactDensity ]: waiting for @inFullscreen change - timed out after 50 tries. -

Categories

(Testing :: mozscreenshots, defect, P1)

Version 3
defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure)

Priority: P5 → P1
There are 31 failures over the last 7 days. These happen on linux64, macosx64, windows10-64, windows7-32. Here is the most recent log example: https://treeherder.mozilla.org/logviewer.html#?repo=autoland&job_id=157949405&lineNumber=7041 Here is a relevant snippet from that log: 12:07:59 ERROR - 4317 INFO TEST-UNEXPECTED-FAIL | browser/tools/mozscreenshots/primaryUI/browser_primaryUI.js | Unexpected exception in [ tabsInTitlebar, fiveTabs, maximized, onlyNavBar, noLWT, compactDensity ]: waiting for @inFullscreen change - timed out after 50 tries. - 12:07:59 INFO - Stack trace: 12:07:59 INFO - chrome://mozscreenshots/content/TestRunner.jsm:_performCombo:361 12:07:59 INFO - 4318 INFO waiting for @inFullscreen change - timed out after 50 tries. 12:07:59 INFO - 4319 INFO Combination 002/540: tabsInTitlebar_fiveTabs_maximized_onlyNavBar_noLWT_normalDensity 12:07:59 INFO - 4320 INFO promising tabsInTitlebar
Flags: needinfo?(MattN+bmo)
These are mostly from the test-verification job running on beta which isn't something that we need to happen. The screenshots job isn't supposed to run on beta so I think we can ignore this recent spike. If someone knows how to skip this job from test verification on beta/release then that would be useful.
Flags: needinfo?(MattN+bmo)
:gbrown- possibly we should ignore test-verify on non-trunk
Flags: needinfo?(gbrown)
See Also: → 1432872
Good idea - bug 1432872.
Flags: needinfo?(gbrown)
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.