Closed Bug 914401 Opened 6 years ago Closed 4 years ago

Intermittent browser_toolbox_raise.js | Test timed out (with TypeError: container is null: toolbox.js:842) or | application timed out after 330 seconds with no output

Categories

(DevTools :: Framework, defect)

All
Windows 8
defect
Not set

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: KWierso, Unassigned)

Details

(Keywords: crash, intermittent-failure, Whiteboard: [test disabled on Windows][leave open])

https://tbpl.mozilla.org/php/getParsedLog.php?id=27597251&tree=Mozilla-Inbound#error1

TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/framework/test/browser_toolbox_raise.js | Test timed out
TypeError: container is null: TBOX_destroy@resource://gre/modules/commonjs/toolkit/loader.js -> resource:///modules/devtools/framework/toolbox.js:842
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/framework/test/browser_toolbox_ready.js | application timed out after 330 seconds with no output
PROCESS-CRASH | chrome://mochitests/content/browser/browser/devtools/framework/test/browser_toolbox_ready.js | application crashed [@ CrashingThread(void *)] 


See log for screenshots.
Did something change on windows 8 recently ? Why does this suddenly starts crashing and all ?
Keywords: crash
And now it suddenly stopped ?
I am thinking that some patch caused it which got backed out due to other reasons.
Skip browser_toolbox_raise.js on Windows. We're assuming for now that the timeout in browser_toolbox_ready.js is just fallout from the first failure and that the test will run OK with _raise skipped.

https://hg.mozilla.org/integration/mozilla-inbound/rev/8785dac97882
Whiteboard: [test disabled on Windows][leave open]
Removing [@ CrashingThread(void *)] since this is just the hang signature, and otherwise results in false positives.
Summary: Intermittent TEST-UNEXPECTED-FAIL | browser_toolbox_raise.js | Test timed out | TypeError: container is null: toolbox.js:842 | browser_toolbox_ready.js | application timed out after 330 seconds with no output | PROCESS-CRASH | [@ CrashingThread(void *)] → Intermittent browser_toolbox_raise.js | Test timed out (with TypeError: container is null: toolbox.js:842) or | application timed out after 330 seconds with no output
Bug 962258 tracks fixing and re-enabling this test (yes, it's still disabled on Windows). Let's let this bug die.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.