Bug 208678

Summary:	[ Mac wk2 Release ] fast/scrolling/scroll-animator-overlay-scrollbars-hovered.html is flaky failing.
Product:	WebKit	Reporter:	Jason Lawrence <Lawrence.j>
Component:	Scrolling	Assignee:	zalan <zalan>
Status:	RESOLVED DUPLICATE
Severity:	Normal	CC:	webkit-bot-watchers-bugzilla, webkit-bug-importer, zalan
Priority:	P2	Keywords:	InRadar
Version:	WebKit Nightly Build
Hardware:	Mac
OS:	macOS 10.15

Jason Lawrence

Reported 2020-03-05 17:13:14 PST

fast/scrolling/scroll-animator-overlay-scrollbars-hovered.html Description: This test is flaky failing on Mac wk2 Release. It does appear to fail more than average after r257840, possibly related to Bug 208577, but it is flaky failing well beyond that, to r252552. History: https://results.webkit.org/?suite=layout-tests&test=fast%2Fscrolling%2Fscroll-animator-overlay-scrollbars-hovered.html&platform=mac&flavor=wk2&style=release&limit=50000 Diff: --- /Volumes/Data/slave/catalina-release-tests-wk2/build/layout-test-results/fast/scrolling/scroll-animator-overlay-scrollbars-hovered-expected.txt +++ /Volumes/Data/slave/catalina-release-tests-wk2/build/layout-test-results/fast/scrolling/scroll-animator-overlay-scrollbars-hovered-actual.txt @@ -1,6 +1,4 @@ -CONSOLE MESSAGE: MainFrameView: didAddVerticalScrollbar -CONSOLE MESSAGE: FrameView: didAddVerticalScrollbar -CONSOLE MESSAGE: FrameView: willRemoveVerticalScrollbar +CONSOLE MESSAGE: line 14: MainFrameView: didAddVerticalScrollbar CONSOLE MESSAGE: line 14: FrameView: didAddVerticalScrollbar CONSOLE MESSAGE: line 14: FrameView: didAddHorizontalScrollbar CONSOLE MESSAGE: line 14: FrameView: willRemoveVerticalScrollbar

Attachments
Add attachment proposed patch, testcase, etc.

Radar WebKit Bug Importer

Comment 1 2020-03-05 17:13:53 PST

<rdar://problem/60108637>

Jason Lawrence

Comment 2 2020-03-05 17:20:04 PST

I have marked this test as failing here: https://trac.webkit.org/changeset/257960/webkit

zalan

Comment 3 2020-03-09 21:32:23 PDT

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

Note You need to log in before you can comment on or make changes to this bug.