Bug 306573

Summary: [MacOS]accessibility/password-notifications-timing.html is a flaky text failure.
Product: WebKit Reporter: Diego De La Toba <d_delatoba>
Component: AccessibilityAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: andresg_22, rackler, webkit-bot-watchers-bugzilla, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   

Diego De La Toba
Reported 2026-01-29 15:13:48 PST
accessibility/password-notifications-timing.html is a flaky text failure on MacOS. HISTORY: https://results.webkit.org/?suite=layout-tests&test=accessibility%2Fpassword-notifications-timing.html DIFF: --- /Volumes/Data/worker/Apple-Tahoe-Release-AppleSilicon-WK2-Tests/build/layout-test-results/accessibility/password-notifications-timing-expected.txt +++ /Volumes/Data/worker/Apple-Tahoe-Release-AppleSilicon-WK2-Tests/build/layout-test-results/accessibility/password-notifications-timing-actual.txt @@ -2,7 +2,7 @@ Field value length: 9 PASS: elapsed >= interval === true -PASS: elapsed >= interval === true +FAIL: elapsed >= interval !== true, was false PASS: elapsed >= interval === true Field value length: 12 DIFF URL: https://build.webkit.org/results/Apple-Tahoe-Release-AppleSilicon-WK2-Tests/306431@main%20(1338)/accessibility/password-notifications-timing-pretty-diff.html STEPS TO REPRODUCE: I was able to reproduce on Tahoe ToT release and debug with the following: run-webkit-tests --no-retry --force —release --iterations 1000 accessibility/password-notifications-timing.html
Attachments
Radar WebKit Bug Importer
Comment 1 2026-01-29 15:13:55 PST
Diego De La Toba
Comment 2 2026-01-29 16:16:07 PST
EWS
Comment 3 2026-02-01 12:57:14 PST
Test gardening commit 306604@main (a37e3596c47a): <https://commits.webkit.org/306604@main> Reviewed commits have been landed. Closing PR #57664 and removing active labels.
Karl Rackler
Comment 4 2026-02-01 12:59:34 PST
The test was introduced with the Debug Skip expectation 295318@main with a comment about skipping due to timing in debug. This same timing issue is affecting release test runs as well, resulting in flaky failures. Modifying test expectation to skip both until this test is fixed.
Note You need to log in before you can comment on or make changes to this bug.