Closed Bug 950430 Opened 6 years ago Closed 6 years ago
_webconsole _chrome .js | Test timed out
https://tbpl.mozilla.org/php/getParsedLog.php?id=31993102&tree=Mozilla-Aurora Ubuntu VM 12.04 mozilla-aurora pgo test mochitest-browser-chrome on 2013-12-14 20:58:23 PST for push cc2ab73484b2 slave: tst-linux32-spot-415 21:28:34 INFO - TEST-PASS | chrome://mochitests/content/browser/browser/devtools/webconsole/test/browser_webconsole_chrome.js | we have an output node 21:29:04 INFO - Xlib: extension "RANDR" missing on display ":0". 21:29:08 INFO - SCREENSHOT: 21:29:08 WARNING - TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/webconsole/test/browser_webconsole_chrome.js | Test timed out 21:29:08 INFO - TEST-INFO | MEMORY STAT vsize after test: 1064296448 21:29:08 INFO - TEST-INFO | MEMORY STAT residentFast after test: 329424896 21:29:08 INFO - TEST-INFO | MEMORY STAT heapAllocated after test: 128456084 21:29:08 INFO - INFO TEST-END | chrome://mochitests/content/browser/browser/devtools/webconsole/test/browser_webconsole_chrome.js | finished in 30139ms
This seems to be a rather odd bug. The intermittent failure happens mostly on aurora pgo? Anything specific there? Maybe we fixed the bug in m-c. I'm making a small change in bug 945489 that might help with this test as well. Not sure what else to do, for now.
Depends on: 945489
The timeouts are... suspicious. The test seems to fail to open the tab or the webconsole, for no obvious reason. There's no logging happening. I rewrote the test to use Task.spawn, and to report once the tab is loaded. r=me Landed: https://hg.mozilla.org/integration/fx-team/rev/c1c8a7310289
Assignee: nobody → mihai.sucan
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 31
You need to log in before you can comment on or make changes to this bug.