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
Again just now: http://build.webkit.org/results/Qt%20Linux%20Release/r53058%20(5809)/results.html
This seems like a pretty basic test to be failing. :(
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.
fast/frames/sandboxed-iframe-navigation-windowopen.html skipped temporarily by http://trac.webkit.org/changeset/53540 to make buildbot happy.
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 .
(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?
It wasn't problem a long time ago, so I closed this bug.