loader/go-back-to-different-window-size.html is flaky
https://bugs.webkit.org/show_bug.cgi?id=96642
Summary loader/go-back-to-different-window-size.html is flaky
Mikhail Pozdnyakov
Reported 2012-09-13 07:12:45 PDT
loader/go-back-to-different-window-size.html is flaky on EFL port.
Attachments
Chris Dumez
Comment 1 2012-09-13 07:38:59 PDT
Would be useful to paste the diff here.
Mikhail Pozdnyakov
Comment 2 2012-09-13 07:41:29 PDT
--- /home/buildslave-1/webkit-buildslave/efl-linux-64-debug/build/layout-test-results/loader/go-back-to-different-window-size-expected.txt +++ /home/buildslave-1/webkit-buildslave/efl-linux-64-debug/build/layout-test-results/loader/go-back-to-different-window-size-actual.txt @@ -1 +1 @@ -PASS +FAIL
Jussi Kukkonen (jku)
Comment 3 2012-12-03 08:55:27 PST
Flaky on Lion, Mountainlion, EFL, GTK. Normally the test finishes in 1sec but a failing test takes 30 seconds, so that's presumable the testrunner notify timeout. The test includes a couple of setTimeout calls to implement this: // Navigation steps: // 1- loads this page // 2- resizes the window to (300, 300) // 3- loads a data URL that resizes the window to (1000, 1000) and navigates back // 4- loads this page which will restore the timer to check the window width to make sure it's > 300 So I'm guessing the the last timer fires before the window width has been reset to 300,300.
Alexey Proskuryakov
Comment 4 2013-09-25 11:11:31 PDT
*** Bug 114274 has been marked as a duplicate of this bug. ***
Alexey Proskuryakov
Comment 5 2013-09-25 11:17:16 PDT
This test is very frequently failing on Mac too. On Mac WK2, the failure is a timeout. On Mac WK1, the whole result is replaced with a result for the previous test (but the previous test is passing). This has to be a bug in the tools that results are copied like that. Unfortunately, I cannot reproduce locally. But window sizing is quite broken in both DRT and WTR, see also bug 110099.
Alexey Proskuryakov
Comment 6 2013-09-25 11:28:45 PDT
Marked as flaky on Mac in r156410. We should probably fix bug 110099 first, and then see how that affects this one.
Note You need to log in before you can comment on or make changes to this bug.