Bug 33303

Summary:	fast/frames/set-unloaded-frame-location.html timed out on Qt Linux Release Build Bot
Product:	WebKit	Reporter:	Eric Seidel (no email) <eric>
Component:	Tools / Tests	Assignee:	Nobody <webkit-unassigned>
Status:	RESOLVED WORKSFORME
Severity:	Normal	CC:	dbates, diegohcg, kent.hansen, mitz, ossy, tonikitoo
Priority:	P2	Keywords:	Qt
Version:	528+ (Nightly build)
Hardware:	PC
OS:	OS X 10.5
Bug Depends on:
Bug Blocks:	33297

Description Eric Seidel (no email) 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

Comment 1 Eric Seidel (no email) 2010-01-10 19:50:48 PST

Again just now:
http://build.webkit.org/results/Qt%20Linux%20Release/r53058%20(5809)/results.html

Comment 2 Eric Seidel (no email) 2010-01-10 19:52:02 PST

This seems like a pretty basic test to be failing. :(

Comment 3 Csaba Osztrogonác 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.

Comment 4 Csaba Osztrogonác 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.

Comment 5 Csaba Osztrogonác 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 .

Comment 6 Kent Hansen 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?

Comment 7 Csaba Osztrogonác 2010-03-16 05:23:08 PDT

It wasn't problem a long time ago, so I closed this bug.