NEW311759
[macOS release] imported/w3c/web-platform-tests/event-timing/keydown is a flaky text failure.
https://bugs.webkit.org/show_bug.cgi?id=311759
Summary [macOS release] imported/w3c/web-platform-tests/event-timing/keydown is a fla...
Diego De La Toba
Reported 2026-04-08 14:44:53 PDT
imported/w3c/web-platform-tests/event-timing/keydown is a flaky text failure on macOS release arm64. HISTORY: https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fevent-timing%2Fkeydown.html&architecture=x86_64 DIFF: --- /Volumes/Data/worker/Apple-Tahoe-Release-AppleSilicon-WK2-Tests/build/layout-test-results/imported/w3c/web-platform-tests/event-timing/keydown-expected.txt +++ /Volumes/Data/worker/Apple-Tahoe-Release-AppleSilicon-WK2-Tests/build/layout-test-results/imported/w3c/web-platform-tests/event-timing/keydown-actual.txt @@ -1,4 +1,6 @@ -PASS Event Timing Keydown. +Harness Error (TIMEOUT), message = null +TIMEOUT Event Timing Keydown. Test timed out + DIFF URL: https://build.webkit.org/results/Apple-Tahoe-Release-AppleSilicon-WK2-Tests/310789@main%20(3116)/imported/w3c/web-platform-tests/event-timing/keydown-pretty-diff.html REPRODUCTION: I was able to reproduce this failure on macOS 26.4 with the following: run-webkit-tests --no-build --no-retry --no-show-results --exit-after-n-failures=1 --expect-pass --iterations=285 --force -f --release imported/w3c/web-platform-tests/event-timing/keydown.html I am going to mark expectations as pass fail while this pends investigation.
Attachments
Radar WebKit Bug Importer
Comment 1 2026-04-08 14:44:59 PDT
Diego De La Toba
Comment 2 2026-04-08 14:49:02 PDT
Test gardening pull request: https://github.com/WebKit/WebKit/pull/62300
EWS
Comment 3 2026-04-08 14:51:02 PDT
Test gardening commit 310797@main (c5a2511f7684): <https://commits.webkit.org/310797@main> Reviewed commits have been landed. Closing PR #62300 and removing active labels.
Diego De La Toba
Comment 4 2026-04-08 18:11:06 PDT
Diego De La Toba
Comment 5 2026-04-09 14:54:30 PDT
Appears to be a timing issue in the test particularly with how it handles performance.now() and event timing 8 millisecond granularity.
Note You need to log in before you can comment on or make changes to this bug.