Bug 267095
Summary: | animations/animation-followed-by-transition.html is a flaky failure | ||
---|---|---|---|
Product: | WebKit | Reporter: | Fujii Hironori <fujii.hironori> |
Component: | Animations | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW | ||
Severity: | Normal | CC: | dino, graouts, graouts, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Fujii Hironori
History:
https://results.webkit.org/?suite=layout-tests&test=animations%2Fanimation-followed-by-transition.html
Buildbot: builder Apple-Ventura-Release-WK1-Tests build 4387 : 269160@main
https://build.webkit.org/#/builders/702/builds/4387
https://build.webkit.org/results/Apple-Ventura-Release-WK1-Tests/269160@main%20(4387)/animations/animation-followed-by-transition-diff.txt
--- /Volumes/Data/worker/Apple-Ventura-Release-WK1-Tests/build/layout-test-results/animations/animation-followed-by-transition-expected.txt
+++ /Volumes/Data/worker/Apple-Ventura-Release-WK1-Tests/build/layout-test-results/animations/animation-followed-by-transition-actual.txt
@@ -1,5 +1,4 @@
Should see animationend followed by transitionend.
animationend
-transitionend
Buildbot: builder Apple-Ventura-Release-WK2-Tests build 4461 : 271369@main
https://build.webkit.org/#/builders/708/builds/4461
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Fujii Hironori
GTK port is marking animations/animation-followed-by-transition.html flaky, but it's not flaky these days on the buildbot.
https://github.com/WebKit/WebKit/blob/7d47c1f87098be0b3c687e5ae1aa27b0c5b54428/LayoutTests/platform/gtk/TestExpectations#L2513
Radar WebKit Bug Importer
<rdar://problem/120860460>
Antoine Quint
Seems more prevalent on WK1 but does happen with WK2.
Antoine Quint
First occurence I find is a test run for 269701@main. Haven't found a failure on an Apple Silicon bot.
Antoine Quint
I'm not able to reproduce the failure when running the test in isolation.
Antoine Quint
Trying to reproduce the failure with a similar test run as a failing bot failed. I'm not sure how to reproduce this as it stands.