Closed
Bug 724193
Opened 12 years ago
Closed 12 years ago
Intermittent test_bug505915.html | Test timed out. followed by havoc in other tests, timing them out and calling finish() on them, winding up terminating the suite
Categories
(Core :: XPConnect, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: philor, Unassigned)
References
Details
(Keywords: intermittent-failure, Whiteboard: [test which aborts the suite])
There are those who would say it's rather naughty to keep on running past your timeout, calling finish() whether or not it's still you that you are calling finish() on. https://tbpl.mozilla.org/php/getParsedLog.php?id=9079655&tree=Mozilla-Inbound Rev3 WINNT 5.1 mozilla-inbound opt test mochitests-4/5 on 2012-02-03 17:22:47 PST for push c831b760a443 374 INFO TEST-START | /tests/js/xpconnect/tests/mochitest/test_bug505915.html 375 ERROR TEST-UNEXPECTED-FAIL | /tests/js/xpconnect/tests/mochitest/test_bug505915.html | Test timed out. If you fixed bug 589668, you'd get a screenshot here 376 INFO TEST-END | /tests/js/xpconnect/tests/mochitest/test_bug505915.html | finished in 317411ms 377 INFO TEST-START | /tests/js/xpconnect/tests/mochitest/test_bug553407.html 378 ERROR TEST-UNEXPECTED-FAIL | /tests/js/xpconnect/tests/mochitest/test_bug553407.html | Test timed out. 379 INFO TEST-UNEXPECTED-FAIL | /tests/js/xpconnect/tests/mochitest/test_bug553407.html | finished in a non-clean fashion (in /tests/js/xpconnect/tests/mochitest/test_bug505915.html) 380 INFO TEST-END | /tests/js/xpconnect/tests/mochitest/test_bug553407.html | finished in 300027ms 381 INFO TEST-START | /tests/js/xpconnect/tests/mochitest/test_bug560351.html 382 ERROR TEST-UNEXPECTED-FAIL | /tests/js/xpconnect/tests/mochitest/test_bug560351.html | Test timed out. 383 INFO TEST-UNEXPECTED-FAIL | /tests/js/xpconnect/tests/mochitest/test_bug560351.html | finished in a non-clean fashion (in /tests/js/xpconnect/tests/mochitest/test_bug505915.html) 384 INFO TEST-END | /tests/js/xpconnect/tests/mochitest/test_bug560351.html | finished in 300026ms 385 INFO TEST-START | /tests/js/xpconnect/tests/mochitest/test_bug564330.html TEST-UNEXPECTED-FAIL | /tests/js/xpconnect/tests/mochitest/test_bug564330.html | application timed out after 330 seconds with no output INFO | automation.py | Application ran for: 0:21:08.203000
Reporter | ||
Updated•12 years ago
|
Whiteboard: [orange] → [orange][test which aborts the suite]
Comment 1•12 years ago
|
||
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that: * Haven't changed in > 6months * Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb} * Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive. I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases). Sorry for the spam! Filter on: #FFA500
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•12 years ago
|
Keywords: intermittent-failure
Assignee | ||
Updated•12 years ago
|
Whiteboard: [orange][test which aborts the suite] → [test which aborts the suite]
You need to log in
before you can comment on or make changes to this bug.
Description
•