Closed Bug 598808 Opened 14 years ago Closed 12 years ago

Intermittent timeout in js/jetpack/tests/unit/test_jetpack.js

Categories

(Core :: JavaScript Engine, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: ehsan.akhgari, Unassigned)

References

Details

(Keywords: intermittent-failure)

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1285200186.1285201676.10142.gz
Rev3 MacOSX Leopard 10.5.8 mozilla-central debug test xpcshell on 2010/09/22 17:03:06

TEST-INFO | /Users/cltbld/talos-slave/mozilla-central_leopard-debug_test-xpcshell/build/xpcshell/tests/js/jetpack/tests/unit/test_jetpack.js | running test ...

command timed out: 1200 seconds without output, killing pid 303
process killed by signal 9
program finished with exit code -1
elapsedTime=1371.116472
TinderboxPrint: xpcshell<br/><em class="testfail">T-FAIL</em>
buildbot.slave.commands.TimeoutError: command timed out: 1200 seconds without output, killing pid 303
TinderboxPrint: xpcshell<br/><em class="testfail">timeout</em>
Whiteboard: [random] → [orange]
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
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.