NEW 289109
REGRESSION(283087@main?): [ iOS ] imported/w3c/web-platform-tests/css/css-view-transitions/transition-skipped-after-animation-started.html is a flaky crash.
https://bugs.webkit.org/show_bug.cgi?id=289109
Summary REGRESSION(283087@main?): [ iOS ] imported/w3c/web-platform-tests/css/css-vie...
Yasmin Karimi
Reported 2025-03-04 12:52:43 PST
Created attachment 474449 [details] imported/w3c/web-platform-tests/css/css-view-transitions/transition-skipped-after-animation-started.html imported/w3c/web-platform-tests/css/css-view-transitions/transition-skipped-after-animation-started.html This test is a flaky crash on iOS. HISTORY: https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fcss%2Fcss-view-transitions%2Ftransition-skipped-after-animation-started.html STDERR: Attached REPRODUCIBILITY: I was unable to reproduce on the iOS 18.2 simulator. REGRESSION: Contextual information indicates the probable regression point is 283087@main. The code paths changed in that commit appear to be directly related to the observed regression test failure. This shows the regression more clearly: https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fcss%2Fcss-view-transitions%2Ftransition-skipped-after-animation-started.html&recent=false&version_name=iOS%2018&version_name=iOS%2017
Attachments
imported/w3c/web-platform-tests/css/css-view-transitions/transition-skipped-after-animation-started.html (191 bytes, text/plain)
2025-03-04 20:52 PST, Yasmin Karimi
no flags
Radar WebKit Bug Importer
Comment 1 2025-03-04 12:52:52 PST
EWS
Comment 2 2025-03-04 13:05:14 PST
Test gardening commit 291587@main (8a8e8d434933): <https://commits.webkit.org/291587@main> Reviewed commits have been landed. Closing PR #41872 and removing active labels.
Alexey Proskuryakov
Comment 3 2025-03-04 13:17:44 PST
I checked several test runs and a bot, and couldn't find a coach log. So this looks more like an unexpected exit than an actual crash (not that it's any better or worse).
Note You need to log in before you can comment on or make changes to this bug.