Closed
Bug 465475
Opened 16 years ago
Closed 16 years ago
"timed out waiting for reftest-wait to be removed" in /layout/reftests/bugs/413292-1.html
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
FIXED
mozilla1.9.1b3
People
(Reporter: dholbert, Assigned: roc)
References
()
Details
(Keywords: fixed1.9.1)
Attachments
(2 files)
519 bytes,
patch
|
Details | Diff | Splinter Review | |
1.12 KB,
patch
|
Details | Diff | Splinter Review |
According to https://wiki.mozilla.org/Tinderbox/Nov-2008-Orange-Compendium, the test "413292-1.html" has sporadically timed out twice today (11/17) and also twice last Tuesday (11/11). I'm guessing that it's also timed out without being noted on the Compendium on other days, too.
The failure is:
REFTEST TEST-UNEXPECTED-FAIL | file:///builds/slave/trunk_linux-8/build/layout/reftests/bugs/413292-1.html | timed out waiting for reftest-wait to be removed (after onload fired)
So far, this has happened twice on moz2-linux-slave07, once on moz2-linux-slave08, and once on moz2-win32-slave07.
Here are the relevant logs:
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1226983046.1226986577.10789.gz&fulltext=1
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1226940673.1226945806.11914.gz&fulltext=1
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1226437998.1226441805.10673.gz&fulltext=1
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1226389049.1226394771.6229.gz&fulltext=1
The test itself is here:
http://mxr.mozilla.org/mozilla-central/source/layout/reftests/bugs/413292-1.html
Reporter | ||
Comment 1•16 years ago
|
||
Note that this reftest takes 3-4 seconds to complete on my (fast) machine. My guess is that on a slow & loaded-down tinderbox, this test may occasionally not quite finish during the 10-second reftest time limit -- i.e. it's timing out because it's just a really long test.
CC'ing roc, who added the test -- roc, do you agree with this diagnosis? And if so, would it be possible to shorten the reftest a bit so that it's less likely to sporadically fail?
Assignee | ||
Comment 2•16 years ago
|
||
Sure, just decrease the iteration count from 20 to 10 or whatever.
Reporter | ||
Comment 3•16 years ago
|
||
Reporter | ||
Comment 4•16 years ago
|
||
Pushed patch (attachment 348721 [details] [diff] [review]) as http://hg.mozilla.org/mozilla-central/rev/c8fb5d5f16e4
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 5•16 years ago
|
||
Still failing on Nov 19:
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1227091046.1227096921.6997.gz
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 6•16 years ago
|
||
I've got an idea. How about we rewrite looop so instead of stopping after a fixed number of iterations, it keeps going for 3 seconds and then stops?
Yeah, just failed again.
Assignee | ||
Updated•16 years ago
|
Assignee: nobody → roc
Flags: wanted1.9.1?
Assignee | ||
Comment 8•16 years ago
|
||
This restores the loopcount to 20 but adds an additional check to stop (and succeed) if we've taken more than 5 seconds. That gives us five seconds to complete the last iteration before hitting the reftest timeout --- I hope that's enough!
Assignee | ||
Updated•16 years ago
|
Whiteboard: [needs landing]
Assignee | ||
Comment 9•16 years ago
|
||
Pushed to trunk as 1a51935c654b
Status: REOPENED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → FIXED
Whiteboard: [needs landing] → [needs 1.9.1 landing]
You need to log in
before you can comment on or make changes to this bug.
Description
•