Closed Bug 605564 Opened 14 years ago Closed 12 years ago

intermittent "TEST-UNEXPECTED-FAIL | reftest/tests/layout/base/crashtests/128855-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:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: jdm, Unassigned)

References

Details

(Keywords: intermittent-failure) 

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1287511582.1287513340.2708.gz
WINNT 5.2 mozilla-central debug test crashtest on 2010/10/19 11:06:22

s: w32-ix-slave35
TEST-UNEXPECTED-FAIL | file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/128855-1.html | application timed out after 330 seconds with no output
buildbot.slave.commands.TimeoutError: command timed out: 1200 seconds without output
Summary: TEST-UNEXPECTED-FAIL | reftest/tests/layout/base/crashtests/128855-1.html | application timed out after 330 seconds with no output → intermittent "TEST-UNEXPECTED-FAIL | reftest/tests/layout/base/crashtests/128855-1.html | application timed out after 330 seconds with no output" or "timed out waiting for onload to fire"
Version: unspecified → Trunk
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1296003832.1296005033.5643.gz
WINNT 5.2 comm-central-trunk debug test crashtest on 2011/01/25 17:03:52
s: cb-seamonkey-win32-01
{
REFTEST TEST-UNEXPECTED-FAIL | file:///e:/builds/slave/test/build/reftest/tests/layout/base/crashtests/128855-1.html | timed out waiting for onload to fire
}
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.