REOPENED 124933
svg/animations/getCurrentTime-pause-unpause.html is flaky 
https://bugs.webkit.org/show_bug.cgi?id=124933
Summary svg/animations/getCurrentTime-pause-unpause.html is flaky
Michal Pakula vel Rutka
Reported 2013-11-27 05:47:40 PST
Layout test svg/animations/getCurrentTime-pause-unpause.html is flaky according to flakines dashboard: http://webkit-test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=svg%2Fanimations%2FgetCurrentTime-pause-unpause.html Test result: --- /mnt/buildbot/efl-linux-slave-2/efl-linux-64-release-wk2/build/layout-test-results/svg/animations/getCurrentTime-pause-unpause-expected.txt +++ /mnt/buildbot/efl-linux-slave-2/efl-linux-64-release-wk2/build/layout-test-results/svg/animations/getCurrentTime-pause-unpause-actual.txt @@ -1,4 +1,4 @@ PASS svg.getCurrentTime() is 0 -PASS svg.getCurrentTime() is 0.05 -PASS svg.getCurrentTime() is 0.05 +FAIL svg.getCurrentTime() should be close to 0.05. Was 0.0770564079284668. +FAIL svg.getCurrentTime() should be close to 0.05. Was 0.07780309021472931.
Attachments
Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2013-12-23 12:22:57 PST
Flaky on all Mac bots, too. Not a recent regression. Sample failure: @@ -1,4 +1,4 @@ PASS svg.getCurrentTime() is 0 -PASS svg.getCurrentTime() is 0.05 -PASS svg.getCurrentTime() is 0.05 +FAIL svg.getCurrentTime() should be close to 0.05. Was 0.13932637870311737. +FAIL svg.getCurrentTime() should be close to 0.05. Was 0.14513742923736572. Marked as flaky in <http://trac.webkit.org/r161011>.
Radar WebKit Bug Importer
Comment 2 2025-02-25 16:24:03 PST
<rdar://problem/145614016>
Fady Farag
Comment 3 2025-02-25 16:26:19 PST
Pull request: https://github.com/WebKit/WebKit/pull/41345
EWS
Comment 4 2025-02-27 08:54:07 PST
Test gardening commit 291229@main (e846714d3164): <https://commits.webkit.org/291229@main> Reviewed commits have been landed. Closing PR #41345 and removing active labels.
Ben Schwartz
Comment 5 2025-02-27 13:15:35 PST
Errantly closed, still happening on macOS.
Note You need to log in before you can comment on or make changes to this bug.