708340 - Intermittent test_bug614757.xul | application timed out after 330 seconds with no output

Status: RESOLVED WORKSFORME

(Core :: XPConnect, defect)

Description

[Phil Ringnalda (:philor)]

https://tbpl.mozilla.org/php/getParsedLog.php?id=7800615&tree=Firefox
Rev3 WINNT 5.1 mozilla-central pgo test mochitest-other on 2011-12-07 09:32:50 PST for push 489f2d51b011

11713 INFO TEST-START | chrome://mochitests/content/chrome/js/xpconnect/tests/chrome/test_bug614757.xul
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/js/xpconnect/tests/chrome/test_bug614757.xul | application timed out after 330 seconds with no output
If you fixed bug 589668, you'd get a screenshot here
INFO | automation.py | Application ran for: 0:07:08.890000

Comment 1

[Ed Morley [:emorley]]

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