RESOLVED FIXED207003
[ macOS wk2 ] tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-overflow.html is flaky failing 
https://bugs.webkit.org/show_bug.cgi?id=207003
Summary [ macOS wk2 ] tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-overf...
Jacob Uphoff
Reported 2020-01-30 09:05:10 PST
tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-overflow.html This test has been a flaky failure for all visible history I was not able to reproduce with iterations runs History: https://results.webkit.org/?suite=layout-tests&test=tiled-drawing%2Fscrolling%2Fscroll-snap%2Fscroll-snap-mandatory-overflow.html Diff: --- /Volumes/Data/slave/catalina-release-tests-wk2/build/layout-test-results/tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-overflow-expected.txt +++ /Volumes/Data/slave/catalina-release-tests-wk2/build/layout-test-results/tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-overflow-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
Attachments
Update Test Expectations (1.50 KB, patch)
2020-01-30 09:13 PST, Jacob Uphoff 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2020-01-30 09:05:37 PST
<rdar://problem/59030072>
Jacob Uphoff
Comment 2 2020-01-30 09:13:50 PST
Created attachment 389254 [details] Update Test Expectations
Truitt Savell
Comment 3 2020-01-30 09:15:43 PST
Comment on attachment 389254 [details] Update Test Expectations Clearing flags on attachment: 389254 Committed r255430: <https://trac.webkit.org/changeset/255430>
Ryan Haddad
Comment 4 2020-04-08 23:01:54 PDT
The test is consistently passing now. Removed expectation in r259782.
Note You need to log in before you can comment on or make changes to this bug.