Bug 172148

Summary: tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-mainframe-vertical.html is still flaky after r209070
Product: WebKit Reporter: Matt Lewis <jlewis3>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: ryanhaddad, wenson_hsieh
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=165196
https://bugs.webkit.org/show_bug.cgi?id=148407

Description Matt Lewis 2017-05-15 17:24:29 PDT
The test tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-mainframe-vertical.html is a flaky failure still.

A proposed fix was given in r209070 https://trac.webkit.org/changeset/209070/webkit

History:
https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=tiled-drawing%2Fscrolling%2Fscroll-snap%2Fscroll-snap-mandatory-mainframe-vertical.html

The test was still flaky on El Capitan and Sierra.
https://build.webkit.org/results/Apple%20El%20Capitan%20Release%20WK2%20(Tests)/r216883%20(1543)/results.html
https://build.webkit.org/builders/Apple%20El%20Capitan%20Release%20WK2%20(Tests)/builds/1543

Diff
--- /Volumes/Data/slave/elcapitan-release-tests-wk2/build/layout-test-results/tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-mainframe-vertical-expected.txt
+++ /Volumes/Data/slave/elcapitan-release-tests-wk2/build/layout-test-results/tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-mainframe-vertical-actual.txt
@@ -1,6 +1,7 @@
 PASS div scrolled to next window.
-PASS div honored snap points.
+FAIL div did not snap back to proper location. (610 vs. 600)
 PASS successfullyParsed is true
+Some tests failed.
 
 TEST COMPLETE
Comment 1 Matt Lewis 2017-05-17 13:56:13 PDT
I have been unable to reproduce the failure on both debug and release for Sierra.
Comment 2 Matt Lewis 2017-07-24 09:42:27 PDT
Marked as flaky failure on Mac WK2:
https://trac.webkit.org/changeset/219825/webkit
Comment 3 Wenson Hsieh 2017-07-24 09:44:01 PDT

*** This bug has been marked as a duplicate of bug 165196 ***