fast/repaint/no-animation-outside-viewport-subframe.html has started to frequently fail on December 16. It's not a true failure, but a problem anyway. For some reason, waitUntilDone watchdog timer fires almost immediately - logs say that the test timed out, but also that it only took 0.1 second! https://build.webkit.org/builders/Apple%20Mavericks%20Release%20WK2%20(Tests)/builds/10221/steps/layout-test/logs/stdio 11:28:23.653 74860 Tests that timed out or crashed: ... 11:28:23.654 74860 fast/repaint/no-animation-outside-viewport-subframe.html took 0.1 seconds
Antti wrote this test, maybe he has an idea.
This looks like a problem with deeper WebCore or DumpRenderTree machinery, like DOM timers being broken.
This happens on other tests too, just happened for the first time on fast/text/international/lang-sensitive-fonts-xml.xhtml. So far, looks like WebKit2 only.
My theory is that this is some deficiency in WebKitTestRunner watchdog timer behavior, we might leak it across tests. Looking into this.
The reason why this regressed is that I unskipped a test that breaks a consequent test 30 seconds later!
Created attachment 243579 [details] proposed fix
Comment on attachment 243579 [details] proposed fix View in context: https://bugs.webkit.org/attachment.cgi?id=243579&action=review > Tools/WebKitTestRunner/InjectedBundle/TestRunner.cpp:165 > + // than to let webkitpy do that, becasue WebKitTestRunner will dump partial results. Nit: ", because" => because
Do we need something similar for DumpRenderTree?
> Do we need something similar for DumpRenderTree? I'm checking that. It looks like the bug exists there too, but it's much less of a problem due to the timer being a global.
Committed <http://trac.webkit.org/r177598>.
Actually, DumpRenderTree seems fine, we always go through dumpTestResults() there.