legacy-animation-engine/animations/stop-animation-on-suspend.html Description: This test is flaky failing on iOS release. History: https://results.webkit.org/?suite=layout-tests&test=legacy-animation-engine%2Fanimations%2Fstop-animation-on-suspend.html Diff: --- /Volumes/Data/slave/ios-simulator-13-release-tests-wk2/build/layout-test-results/legacy-animation-engine/animations/stop-animation-on-suspend-expected.txt +++ /Volumes/Data/slave/ios-simulator-13-release-tests-wk2/build/layout-test-results/legacy-animation-engine/animations/stop-animation-on-suspend-actual.txt @@ -1,6 +1,6 @@ PASS - "webkitTransform" property for "box" element at 0.2s saw something close to: 1,0,0,1,100,0 PASS - "webkitTransform" property for "iframe.subframe-box" element at 0.2s saw something close to: 1,0,0,1,100,0 -PASS - "webkitTransform" property for "box" element at 0.4s saw something close to: 1,0,0,1,200,0 -PASS - "webkitTransform" property for "iframe.subframe-box" element at 0.4s saw something close to: 1,0,0,1,200,0 +FAIL - "webkitTransform" property for "box" element at 0.4s expected: 1,0,0,1,200,0 but saw: matrix(1, 0, 0, 1, 126.72084045410156, 0) +FAIL - "webkitTransform" property for "iframe.subframe-box" element at 0.4s expected: 1,0,0,1,200,0 but saw: matrix(1, 0, 0, 1, 126.85371398925781, 0)
This test is marked as flaky on macOS, see bug 49182. It is curious that failures are most common on iOS Release, but scrolling back in history, I see them on debug too. This is not a new regression.
Created attachment 388907 [details] Update Test Expectations
Created attachment 388911 [details] Update Test Expectations
Comment on attachment 388911 [details] Update Test Expectations Clearing flags on attachment: 388911 Committed r255177: <https://trac.webkit.org/changeset/255177>
I was able to reproduce this issue locally by running the following command: ’run-webkit-tests legacy-animation-engine/animations/stop-animation-on-suspend.html --iterations 5000 -f --ios-simulator’ 4994 tested ran as expected, 6 didn’t.
This test is gone as of r258150, see bug 208815.
<rdar://problem/60238048>