The test animations/needs-layout.html is a flaky image failure on macOS Sierra. It has failed on WK1 release and WK2 Debug. The test seems to have been flaky from when it was added. https://trac.webkit.org/changeset/217075/webkit https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=animations%2Fneeds-layout.html https://build.webkit.org/builders/Apple%20Sierra%20Debug%20WK2%20(Tests)/builds/1103 https://build.webkit.org/results/Apple%20Sierra%20Debug%20WK2%20(Tests)/r217140%20(1103)/results.html I was able to reproduce the failure in Sierra debug with: run-webkit-tests animations/needs-layout.html --debug --no-retry-failure --iterations=50 -f
This is a new test, just added in bug 172300. Dean, can you take a look please?
Marked test as flaky: https://trac.webkit.org/changeset/219166/webkit
This failure has since started on El Capitan Debug and iOS Simulator Debug: https://build.webkit.org/builders/Apple%20El%20Capitan%20Debug%20WK2%20(Tests)/builds/2801 https://build.webkit.org/builders/Apple%20iOS%2010%20Simulator%20Debug%20WK2%20(Tests)/builds/3608
Adjusted Expectations: https://trac.webkit.org/changeset/224239/webkit
This test is now flaky on release, too.
Created attachment 338050 [details] Patch
Comment on attachment 338050 [details] Patch Attachment 338050 [details] did not pass mac-debug-ews (mac): Output: http://webkit-queues.webkit.org/results/7336578 New failing tests: legacy-animation-engine/css3/masking/clip-path-animation.html
Created attachment 338064 [details] Archive of layout-test-results from ews116 for mac-sierra The attached test failures were seen while running run-webkit-tests on the mac-debug-ews. Bot: ews116 Port: mac-sierra Platform: Mac OS X 10.12.6
(In reply to Build Bot from comment #7) > Comment on attachment 338050 [details] > Patch > > Attachment 338050 [details] did not pass mac-debug-ews (mac): > Output: http://webkit-queues.webkit.org/results/7336578 > > New failing tests: > legacy-animation-engine/css3/masking/clip-path-animation.html This crash should not be related to this patch which only affects the code path used for the new animation engine. This test uses the legacy animation engine and the ASSERT reached in FrameView is conditioned to only run on the legacy code path, so we are indeed not using the new one.
Committed r230703: <https://trac.webkit.org/changeset/230703>
*** Bug 184638 has been marked as a duplicate of this bug. ***
<rdar://problem/39483712>