RESOLVED FIXED 168924
[ios-simulator WK2] LayoutTest scrollingcoordinator/ios/non-stable-viewport-scroll.html is a flaky failure
https://bugs.webkit.org/show_bug.cgi?id=168924
Summary [ios-simulator WK2] LayoutTest scrollingcoordinator/ios/non-stable-viewport-s...
Ryan Haddad
Reported 2017-02-27 12:47:56 PST
LayoutTest scrollingcoordinator/ios/non-stable-viewport-scroll.html is a flaky failure https://build.webkit.org/results/Apple%20iOS%2010%20Simulator%20Debug%20WK2%20(Tests)/r213044%20(3810)/results.html https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#tests=scrollingcoordinator%2Fios%2Fnon-stable-viewport-scroll.html --- /Volumes/Data/slave/ios-simulator-10-debug-tests-wk2/build/layout-test-results/scrollingcoordinator/ios/non-stable-viewport-scroll-expected.txt +++ /Volumes/Data/slave/ios-simulator-10-debug-tests-wk2/build/layout-test-results/scrollingcoordinator/ios/non-stable-viewport-scroll-actual.txt @@ -16,14 +16,13 @@ (contentsScale 6.00) (children 1 (GraphicsLayer - (position 10.00 0.00) - (approximate position 10.00 634.67) + (position 10.00 635.00) (bounds 100.00 548.00) (usingTiledLayer 1) (contentsOpaque 1) (drawsContent 1) - (visible rect 0.00, 365.33 96.67 x 182.67) - (coverage rect -10.00, 322.66 192.00 x 268.00) + (visible rect 0.00, 365.00 96.67 x 182.67) + (coverage rect -10.00, 322.33 192.00 x 268.00) (intersects coverage rect 1) (contentsScale 6.00) )
Attachments
Patch (2.71 KB, patch)
2019-03-09 21:44 PST, Simon Fraser (smfr)
no flags
Ryan Haddad
Comment 1 2017-02-27 17:16:55 PST
The earliest failure on the flakiness dashboard is 2/17/2017 4:23:29 PM @ r212591, though the failure is flaky and that change is unrelated.
Alexey Proskuryakov
Comment 2 2017-02-27 19:31:32 PST
I see this produce spurious EWS failures.
Ryan Haddad
Comment 3 2017-03-06 15:34:21 PST
Simon Fraser (smfr)
Comment 4 2019-03-09 21:44:32 PST
Simon Fraser (smfr)
Comment 5 2019-03-09 21:53:35 PST
Radar WebKit Bug Importer
Comment 6 2019-03-09 21:58:34 PST
Note You need to log in before you can comment on or make changes to this bug.