Bug 222332

Summary: [ macOS BigSur Wk2 ] compositing/video/video-border-radius-clipping.html is a flakey image failure
Product: WebKit Reporter: Robert Jenner <jenner>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: ap, tsavell, webkit-bot-watchers-bugzilla, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=224690
Attachments:
Description Flags
Diff Image
none
Patch
none
Patch none

Description Robert Jenner 2021-02-23 14:20:16 PST 
Created attachment 421350 [details]
Diff Image

compositing/video/video-border-radius-clipping.html

Is a flakey image failure in macOS Wk2 release. 

HISTORY URL:
https://results.webkit.org/?suite=layout-tests&test=compositing%2Fvideo%2Fvideo-border-radius-clipping.html&platform=mac

Images URL:
https://build.webkit.org/results/Apple-BigSur-Release-WK2-Tests/r273321%20(451)/compositing/video/video-border-radius-clipping-diffs.html

DIFF Image has been attached.
Comment 1 Robert Jenner 2021-02-23 14:23:25 PST 
The test expectation is currently labeled as [ Pass Failure Timeout ], and that appears to be setting unrealistic test expectations. Before we work on bisecting to discover a regress point, we are going to update the test results to [ Pass ImageOnlyFailure ]
Comment 2 Radar WebKit Bug Importer 2021-02-23 14:23:40 PST 
<rdar://problem/74661364>
Comment 3 Robert Jenner 2021-02-23 14:33:34 PST 
Created attachment 421352 [details]
Patch
Comment 4 Robert Jenner 2021-02-23 14:51:35 PST 
Created attachment 421353 [details]
Patch
Comment 5 Truitt Savell 2021-02-23 14:56:18 PST 
Comment on attachment 421353 [details]
Patch

Clearing flags on attachment: 421353

Committed r273355 (234488@main): <https://commits.webkit.org/234488@main>
Comment 6 Robert Jenner 2021-02-23 15:44:14 PST 
Could not reproduce flakey image failure. It is possible that the issue was with the prior test expectation that was set, and not with the test itself. We are going to observe the test history over the next few days before we proceed on this bug.