Closed Bug 497602 Opened 16 years ago Closed 12 years ago

crashtest: intermittent "265986-1.html | timed out waiting for onload to fire"

Categories

(Core :: Layout: Block and Inline, defect)

1.9.1 Branch
x86
All
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: sgautherie, Unassigned)

References

(Blocks 1 open bug, )

Details

(Keywords: intermittent-failure)

{ http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1244696288.1244700645.24962.gz WINNT 5.2 comm-central unit test on 2009/06/10 21:58:08 REFTEST TEST-UNEXPECTED-FAIL | file:///e:/builds/slave/comm-central-win32-unittest/build/mozilla/layout/base/crashtests/265986-1.html | timed out waiting for onload to fire }
OS: Windows Server 2003 → All
Whiteboard: [orange]
This test has a gigantic <marquee>, so it might be the same bug as bug 509527.
Depends on: 509527
Summary: [SeaMonkey] crashtest: intermittent "265986-1.html | timed out waiting for onload to fire" → crashtest: intermittent "265986-1.html | timed out waiting for onload to fire"
Depends on: 564234
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.