RESOLVED WORKSFORME Bug 33303
fast/frames/set-unloaded-frame-location.html timed out on Qt Linux Release Build Bot
https://bugs.webkit.org/show_bug.cgi?id=33303
Summary fast/frames/set-unloaded-frame-location.html timed out on Qt Linux Release Bu...
Eric Seidel (no email)
Reported 2010-01-06 21:47:40 PST
fast/frames/set-unloaded-frame-location.html timed out on Qt Linux Release Build Bot This is the first time I've noticed this failure: http://build.webkit.org/results/Qt%20Linux%20Release/r52900%20(5657)/results.html This test has been in the repository forever: http://trac.webkit.org/browser/trunk/LayoutTests/fast/frames/set-unloaded-frame-location.html
Attachments
Eric Seidel (no email)
Comment 1 2010-01-10 19:50:48 PST
Eric Seidel (no email)
Comment 2 2010-01-10 19:52:02 PST
This seems like a pretty basic test to be failing. :(
Csaba Osztrogonác
Comment 3 2010-01-20 03:28:39 PST
from r53526~r53528 it timed out always :S I wasn't able to reproduce it with WebKitTools/Scripts/run-webkit-tests fast/frames/set-unloaded-frame-location.html --iterations 1000. I ran WebKitTools/Scripts/run-webkit-tests fast/frames/ --iterations 100, and fast/frames/set-unloaded-frame-location.html timed out again and again. If I skipped it, fast/frames/valid.html timed out again and again. Finally I found the root of the problem: fast/frames/sandboxed-iframe-navigation-windowopen.html. I presume this test case leave some mess in DRT.
Csaba Osztrogonác
Comment 4 2010-01-20 03:38:50 PST
fast/frames/sandboxed-iframe-navigation-windowopen.html skipped temporarily by http://trac.webkit.org/changeset/53540 to make buildbot happy.
Csaba Osztrogonác
Comment 5 2010-02-02 04:11:29 PST
I unskipped the test and ran "WebKitTools/Scripts/run-webkit-tests fast/frames/ --iterations 100" on r54216, and it works without any timeout. I have no idea what caused the time outs and which commit fixed it, but it works correctly now, so unskipped the test by http://trac.webkit.org/changeset/54224 .
Kent Hansen
Comment 6 2010-03-16 05:13:32 PDT
(In reply to comment #5) > I unskipped the test and ran "WebKitTools/Scripts/run-webkit-tests fast/frames/ > --iterations 100" on r54216, and it works without any timeout. > > I have no idea what caused the time outs and which commit fixed it, but it > works correctly now, so unskipped the test by > http://trac.webkit.org/changeset/54224 . OK, can this bug be closed as WORKSFORME then?
Csaba Osztrogonác
Comment 7 2010-03-16 05:23:08 PDT
It wasn't problem a long time ago, so I closed this bug.
Note You need to log in before you can comment on or make changes to this bug.