Closed Bug 625182 Opened 9 years ago Closed 7 years ago

Intermittent dom/base/crashtests/504224.html | timed out waiting for reftest-wait to be removed

Categories

(Core :: DOM: Core & HTML, defect)

x86
macOS
defect
Not set

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure)

http://tinderbox.mozilla.org/showlog.cgi?log=TraceMonkey/1294866234.1294866482.14511.gz
Rev3 MacOSX Leopard 10.5.8 tracemonkey opt test crashtest on 2011/01/12 13:03:54
s: talos-r3-leopard-052

REFTEST TEST-START | file:///Users/cltbld/talos-slave/test/build/reftest/tests/dom/base/crashtests/504224.html
REFTEST TEST-UNEXPECTED-FAIL | file:///Users/cltbld/talos-slave/test/build/reftest/tests/dom/base/crashtests/504224.html | timed out waiting for reftest-wait to be removed
REFTEST INFO | Saved log: START file:///Users/cltbld/talos-slave/test/build/reftest/tests/dom/base/crashtests/504224.html
REFTEST INFO | Saved log: OnDocumentLoad triggering WaitForTestEnd
REFTEST INFO | Saved log: WaitForTestEnd: Adding listeners
REFTEST INFO | Saved log: MakeProgress: STATE_WAITING_TO_FIRE_INVALIDATE_EVENT
REFTEST INFO | Saved log: MakeProgress: STATE_WAITING_FOR_REFTEST_WAIT_REMOVAL
REFTEST INFO | Saved log: MakeProgress: waiting for reftest-wait to be removed
REFTEST INFO | Saved log: AfterPaintListener in file:///Users/cltbld/talos-slave/test/build/reftest/tests/dom/base/crashtests/504224.html
REFTEST INFO | Saved log: AfterPaintListener in chrome://reftest/content/reftest.xul
REFTEST INFO | Saved log: MakeProgress: STATE_WAITING_FOR_REFTEST_WAIT_REMOVAL
REFTEST INFO | Saved log: MakeProgress: waiting for reftest-wait to be removed
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: 7 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.