Bug 209293 - REGRESSION: [ Mac WK2 ] tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-borders.html is a flaky failure
Summary: REGRESSION: [ Mac WK2 ] tiled-drawing/scrolling/scroll-snap/scroll-snap-manda...
Status: RESOLVED DUPLICATE of bug 165196
Alias: None
Product: WebKit
Classification: Unclassified
Component: Scrolling (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2020-03-19 11:04 PDT by Truitt Savell
Modified: 2020-03-20 09:23 PDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Truitt Savell 2020-03-19 11:04:09 PDT
tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-borders.html 

This test began failing recently. I am able to reproduce the failure with this command:

run-webkit-tests --iterations 2000 --exit-after-n-failures 1 --exit-after-n-crashes-or-timeouts 1 --debug-rwt-logging --no-retry --force --no-build -f tiled-drawing/scrolling/scroll-iframe-latched-selects.html

History:
https://results.webkit.org/?suite=layout-tests&test=tiled-drawing%2Fscrolling%2Fscroll-snap%2Fscroll-snap-mandatory-borders.html

Diff:
--- /Volumes/Data/slave/catalina-debug-tests-wk2/build/layout-test-results/tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-borders-expected.txt
+++ /Volumes/Data/slave/catalina-debug-tests-wk2/build/layout-test-results/tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-borders-actual.txt
@@ -4,10 +4,11 @@
 Testing scroll-snap snap for horizontalTarget:
 PASS div honored snap points.
 Testing scroll-snap glide for verticalTarget:
-PASS div scrolled to next window.
+FAIL div did not honor snap points. Expected 300, but got 0
 Testing scroll-snap snap for verticalTarget:
 PASS div honored snap points.
 PASS successfullyParsed is true
+Some tests failed.
 
 TEST COMPLETE
Comment 1 Radar WebKit Bug Importer 2020-03-19 11:06:59 PDT
<rdar://problem/60641337>
Comment 2 Simon Fraser (smfr) 2020-03-20 09:23:58 PDT
Pretty sure that https://trac.webkit.org/changeset/258753/webkit fixed this.

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