Closed Bug 612781 Opened 14 years ago Closed 12 years ago

Intermittent crashtest harness timeout in "layout/base/crashtests/275746-1.html | application timed out after 330 seconds with no output" or "timed out waiting for onload to fire"

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Platform:
All
Windows Server 2003
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: dholbert, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [test that aborts the suite] )

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1289954125.1289955937.21452.gz TEST-UNEXPECTED-FAIL | file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/275746-1.html | application timed out after 330 seconds with no output WINNT 5.2 mozilla-central debug test crashtest on 2010/11/16 16:35:25 s: w32-ix-slave22 command timed out: 1200 seconds without output program finished with exit code 1 elapsedTime=1661.062000 TinderboxPrint: crashtest<br/><em class="testfail">T-FAIL</em> buildbot.slave.commands.TimeoutError: command timed out: 1200 seconds without output
Summary: sporadic crashtest timeout in layout/base/crashtests/275746-1.html | application timed out after 330 seconds with no output → Intermittent crashtest harness timeout in layout/base/crashtests/275746-1.html | application timed out after 330 seconds with no output
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1292650757.1292653436.26852.gz WINNT 5.2 comm-central-trunk debug test crashtest on 2010/12/17 21:39:17 { REFTEST TEST-UNEXPECTED-FAIL | file:///e:/builds/slave/test/build/reftest/tests/layout/base/crashtests/275746-1.html | timed out waiting for onload to fire }
URL: http://tinderbox.mozilla.org/showlog....
Severity: normal → major
Summary: Intermittent crashtest harness timeout in layout/base/crashtests/275746-1.html | application timed out after 330 seconds with no output → Intermittent crashtest harness timeout in "layout/base/crashtests/275746-1.html | application timed out after 330 seconds with no output" or "timed out waiting for onload to fire"
Whiteboard: [orange][test that aborts the suite] → [test that aborts the suite] [orange]
Depends on: 633718
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: [test that aborts the suite] [orange] → [test that aborts the suite]
You need to log in before you can comment on or make changes to this bug.