Closed Bug 1549250 Opened 5 years ago Closed 5 years ago

Intermittent toolkit/mozapps/extensions/test/xpinstall/browser_bug540558.js | Test timed out -

Categories

(Toolkit :: Add-ons Manager, defect, P5)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure, regression, Whiteboard: [stockwell])

Filed by: dvarga [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=244783247&repo=autoland
Full log: https://queue.taskcluster.net/v1/task/f-H1NjjQR1iwIziDgmqVGg/runs/0/artifacts/public/logs/live_backing.log


01:18:35 INFO - TEST-PASS | toolkit/mozapps/extensions/test/xpinstall/browser_bug540558.js | Should have seen the expected number of installs started -
01:18:35 INFO - Console message: [JavaScript Error: "The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol." {file: "http://example.com/browser/toolkit/mozapps/extensions/test/xpinstall/bug540558.html" line: 0}]
01:18:35 INFO - Console message: 1557105425335 addons.xpi DEBUG Download started for http://example.com/browser/toolkit/mozapps/extensions/test/xpinstall/amosigned.xpi to file C:\Users\task_1557099123\AppData\Local\Temp\tmp-61k.xpi
01:18:35 INFO - Console message: 1557105425336 addons.xpi DEBUG Download of http://example.com/browser/toolkit/mozapps/extensions/test/xpinstall/amosigned.xpi completed.
01:18:35 INFO - Console message: 1557105425391 addons.repository DEBUG cacheAddons: enabled false IDs ["amosigned-xpi@tests.mozilla.org"]
01:18:35 INFO - Buffered messages logged at 01:17:25
01:18:35 INFO - Console message: 1557105445455 addons.productaddons INFO Updates are disabled via media.gmp-manager.updateEnabled
01:18:35 INFO - Buffered messages finished
01:18:35 INFO - TEST-UNEXPECTED-FAIL | toolkit/mozapps/extensions/test/xpinstall/browser_bug540558.js | Test timed out -
01:18:35 INFO - Not taking screenshot here: see the one that was previously logged
01:18:35 INFO - TEST-UNEXPECTED-FAIL | toolkit/mozapps/extensions/test/xpinstall/browser_bug540558.js | Should be no active installs at the end of the test - Got 2, expected 0
01:18:35 INFO - Stack trace:
01:18:35 INFO - chrome://mochikit/content/browser-test.js:test_is:1325
01:18:35 INFO - chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/xpinstall/head.js:setup/<:143
01:18:35 INFO - chrome://mochikit/content/browser-test.js:nextTest:715
01:18:35 INFO - chrome://mochikit/content/browser-test.js:timeoutFn:1212
01:18:35 INFO - setTimeout handlerchrome://mochikit/content/browser-test.js:Tester_execTest:1174
01:18:35 INFO - chrome://mochikit/content/browser-test.js:nextTest/<:1005
01:18:35 INFO - chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<:803
01:18:35 INFO - Install for [xpconnect wrapped nsIURI @ 0xbdfe790 (native @ 0x13a26a04)] is in state 3
01:18:35 INFO - GECKO(3080) | 1557105515098 addons.manager WARN InstallListener threw exception when calling onDownloadCancelled: TypeError: this.webProgress is null(chrome://global/content/elements/browser-custom-element.js:893:5) JS Stack trace: removeProgressListener@browser-custom-element.js:893:5
01:18:35 INFO - GECKO(3080) | unregister@AddonManager.jsm:283:20
01:18:35 INFO - GECKO(3080) | onDownloadCancelled@AddonManager.jsm:315:10
01:18:35 INFO - GECKO(3080) | callInstallListeners@AddonManager.jsm:1351:33
01:18:35 INFO - GECKO(3080) | callInstallListeners@AddonManager.jsm:2796:54
01:18:35 INFO - GECKO(3080) | _callInstallListeners@XPIInstall.jsm:1755:32
01:18:35 INFO - GECKO(3080) | cancel@XPIInstall.jsm:1250:12
01:18:35 INFO - GECKO(3080) | cancel@XPIInstall.jsm:1937:13
01:18:35 INFO - GECKO(3080) | cancel@XPIInstall.jsm:2374:22
01:18:35 INFO - GECKO(3080) | setup/</<@head.js:146:20
01:18:35 INFO - GECKO(3080) | setup/<@head.js:144:19
01:18:35 INFO - GECKO(3080) | async
nextTest@browser-test.js:715:35
01:18:35 INFO - GECKO(3080) | timeoutFn@browser-test.js:1212:14
01:18:35 INFO - GECKO(3080) | setTimeout handler*Tester_execTest@browser-test.js:1174:45
01:18:35 INFO - GECKO(3080) | nextTest/<@browser-test.js:1005:14

In the last 7 days there are 41 failres. All of them on Windows7-32 & Windows7-32-shippable.
It started with Bug 1412561
:pbz , can you please take a look?

Flags: needinfo?(pbz)

Thanks for reaching out. I currently can't think of any way my patch could affect this test and I was not able to reproduce it either.
:aswan, since you also reviewed my patch, could you please advise on this?

Flags: needinfo?(pbz) → needinfo?(aswan)

I noticed from the logs that browser_block_fullscreen_prompt.js is the test that runs right before the test that failed.
And this screenshot looks like maybe the browser is still in full screen mode?
https://taskcluster-artifacts.net/f-H1NjjQR1iwIziDgmqVGg/0/public/test_info/mozilla-test-fail-screenshot_e9xkx8.png

Nothing else obvious jumps out at me from the logs and I don't know a lot about fullscreen and why we might be failing to get out of it, but does that give you enough to debug further?

Flags: needinfo?(aswan)

The browser does not appear to be in full-screen mode any more when it reaches the next test. Here is another screenshot of the test failure on Linux: https://taskcluster-artifacts.net/TXr4HacYQnGdnn4WsIjzJA/0/public/test_info//mozilla-test-fail-screenshot_I94vTb.png
Also, when a tab is closed, in this case the test tab, the browser will leave full-screen.

There seem to be issues with the full-screen addon test though (Bug 1549261), so I'll try to resolve those first to see if it affects this bug.

(In reply to Paul Zühlcke [:pbz] from comment #8)

There seem to be issues with the full-screen addon test though (Bug 1549261), so I'll try to resolve those first to see if it affects this bug.

Sounds good.

There are 155 bugs associated with this bug in the last 7 days.

Platform breakdown:

windows7-32: 84
windows7-32-shippable: 24
linux64: 15
linux32-shippable: 11
linux32: 8
linux64-shippable: 6
linux64-devedition: 1
windows7-32-devedition: 3
linux32-devedition: 1
linux64-ccov: 2

Removing the disable recommended tag

Whiteboard: [stockwell disable-recommended] → [stockwell needswork:owner]
Whiteboard: [stockwell disable-recommended] → [stockwell needswork:owner]

The priority flag is not set for this bug.
:ddurst, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(ddurst)

Removed "needswork:owner", as there haven't been any new occurrences over the last 4 months.

Flags: needinfo?(ddurst)
Priority: -- → P5
Whiteboard: [stockwell needswork:owner] → [stockwell]
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.