Closed Bug 627021 Opened 14 years ago Closed 12 years ago

Intermittent js1_7/regress/regress-462388.js | timed out waiting for onload to fire

Categories

(Core :: JavaScript Engine, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure)

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1295448401.1295449920.9447.gz Rev3 MacOSX Snow Leopard 10.6.2 mozilla-central debug test jsreftest on 2011/01/19 06:46:41 s: talos-r3-snow-009 REFTEST TEST-START | file:///Users/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_7/regress/regress-462388.js ++DOMWINDOW == 14 (0x13cfc36e8) [serial = 5230] [outer = 0x10dee6210] REFTEST TEST-UNEXPECTED-FAIL | file:///Users/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_7/regress/regress-462388.js | timed out waiting for onload to fire REFTEST INFO | Saved log: START file:///Users/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_7/regress/regress-462388.js
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.