Bug 232040

Summary: New test : [ iOS macOS wk2 ] webanimations/marker-opacity-animation-no-effect.html is a flaky image failure
Product: WebKit Reporter: ayumi_kojima
Component: AnimationsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: ap, bfulgham, dino, don.olmstead, graouts, 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=231906
Attachments:
Description Flags
Image diff none

ayumi_kojima
Reported 2021-10-20 13:53:37 PDT
webanimations/marker-opacity-animation-no-effect.html Is a flaky image failure on iOS 15 and macOS wk2. History: https://results.webkit.org/?suite=layout-tests&test=webanimations%2Fmarker-opacity-animation-no-effect.html Result page: https://build.webkit.org/results/Apple-BigSur-Release-WK2-Tests/r284548%20(6019)/results.html
Attachments
Image diff (2.27 KB, image/png)
2021-10-20 13:54 PDT, ayumi_kojima 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2021-10-20 13:54:09 PDT
<rdar://problem/84477684>
ayumi_kojima
Comment 2 2021-10-20 13:54:26 PDT
Created attachment 441930 [details] Image diff
ayumi_kojima
Comment 3 2021-10-20 13:58:13 PDT
Marked test expectations https://trac.webkit.org/changeset/284565/webkit
ayumi_kojima
Comment 4 2021-10-20 16:51:40 PDT
I was able to reproduce the image failure locally using run-webkit-tests --force --iterations 500 --exit-after-n-failures 1 webanimations/marker-opacity-animation-no-effect.html The test passed with r284515 (though this revision failed on the testing bot) and failed with r284516. It looks like https://trac.webkit.org/changeset/284516/webkit caused the flaky image failure, but not sure since I think it is very strange that r284515 failed on the testing bot, but didn't fail locally (iterated 1000 times, but passed.)
Alexey Proskuryakov
Comment 5 2021-10-22 11:21:51 PDT
Yes, it's very unlikely for r284516 to have caused this.
Alexey Proskuryakov
Comment 6 2021-10-22 11:30:56 PDT
I think that it's just a coincidence that the test worked for a few build after having been added, and it's just a flaky test.
Brent Fulgham
Comment 7 2022-06-23 14:43:32 PDT
Ryan and Antoine confirmed this is resolved as of 5/20/2022.
Note You need to log in before you can comment on or make changes to this bug.