Bug 207861
Summary: | [ macOS wk2 ] tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-rotated.html is flaky failing | ||
---|---|---|---|
Product: | WebKit | Reporter: | Jacob Uphoff <jacob_uphoff> |
Component: | Scrolling | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | CC: | simon.fraser, webkit-bot-watchers-bugzilla, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Jacob Uphoff
tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-rotated.html
This test has been a flaky failure for all visible history.
Looks like this failure is happening on wk2 release
I ran the test in iterations x5000 locally and did not reproduce the failure.
History:
https://results.webkit.org/?suite=layout-tests&test=tiled-drawing%2Fscrolling%2Fscroll-snap%2Fscroll-snap-mandatory-rotated.html&limit=50000
Diff:
--- /Volumes/Data/slave/mojave-release-tests-wk2/build/layout-test-results/tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-rotated-expected.txt
+++ /Volumes/Data/slave/mojave-release-tests-wk2/build/layout-test-results/tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-rotated-actual.txt
@@ -1,6 +1,6 @@
Tests that the scroll-snap feature works properly in overflow regions.
Testing scroll-snap glide for horizontalTarget:
-PASS div scrolled to next window.
+FAIL div did not honor snap points. Expected 300, but got 0
Testing scroll-snap snap for horizontalTarget:
PASS div honored snap points.
Testing scroll-snap glide for verticalTarget:
@@ -8,6 +8,7 @@
Testing scroll-snap snap for verticalTarget:
PASS div honored snap points.
PASS successfullyParsed is true
+Some tests failed.
TEST COMPLETE
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Jacob Uphoff
Set expectations here: https://trac.webkit.org/changeset/256776/webkit
Radar WebKit Bug Importer
<rdar://problem/59527478>
Simon Fraser (smfr)
No longer flakey. Expectation removed in r258701.
*** This bug has been marked as a duplicate of bug 197819 ***