Closed Bug 622628 Opened 14 years ago Closed 12 years ago

Intermittent layout/base/crashtests/321077-2.xul | application timed out after 330 seconds with no output

Categories

(Core :: Layout, 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/1294073798.1294074307.29336.gz#err0
Rev3 MacOSX Leopard 10.5.8 mozilla-central opt test crashtest on 2011/01/03 08:56:38
s: talos-r3-leopard-040

REFTEST TEST-START | file:///Users/cltbld/talos-slave/test/build/reftest/tests/layout/base/crashtests/321077-2.xul
REFTEST TEST-PASS | file:///Users/cltbld/talos-slave/test/build/reftest/tests/layout/base/crashtests/321077-2.xul | (LOAD ONLY)
REFTEST INFO | Loading a blank page
TEST-UNEXPECTED-FAIL | file:///Users/cltbld/talos-slave/test/build/reftest/tests/layout/base/crashtests/321077-2.xul | application timed out after 330 seconds with no output
Can't trigger Breakpad, just killing process
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.