307385 2026-02-09 16:00:21 -0800 [MacOS] fast/events/onunload-not-on-body.html is a flaky text failure 2026-03-09 16:17:54 -0700 1 1 1 Unclassified WebKit New Bugs WebKit Nightly Build Unspecified Unspecified RESOLVED DUPLICATE 296199 InRadar P2 Normal --- 1 d_delatoba webkit-unassigned rniwa webkit-bot-watchers-bugzilla webkit-bug-importer oldest_to_newest 2179645 0 d_delatoba 2026-02-09 16:00:21 -0800 fast/events/onunload-not-on-body.html is a flaky text failure across all architectures and styles. HISTORY: https://results.webkit.org/?suite=layout-tests&test=fast%2Fevents%2Fonunload-not-on-body.html TEXT DIFF: --- /Volumes/Data/worker/Apple-Tahoe-Release-AppleSilicon-WK2-Tests/build/layout-test-results/fast/events/onunload-not-on-body-expected.txt +++ /Volumes/Data/worker/Apple-Tahoe-Release-AppleSilicon-WK2-Tests/build/layout-test-results/fast/events/onunload-not-on-body-actual.txt @@ -1,3 +1,3 @@ -frame "<!--frame3-->" - has 1 onunload handler(s) +frame "<!--frame4-->" - has 1 onunload handler(s) CONSOLE MESSAGE: Use of window.alert is not allowed while unloading a page. you should only see one unload alert appear. DIFF URL: https://build.webkit.org/results/Apple-Tahoe-Release-AppleSilicon-WK2-Tests/307099%40main%20(1543)/fast/events/onunload-not-on-body-pretty-diff.html REPRODUCTION: I was able to reproduce this failure on macOS Tahoe ToT arm64 with the following: run-webkit-tests --force --release --no-retry --iterations 1000 fast/events/onunload-not-on-body.html I am going to mark expectations as pass fail while this pends investigation. 2179646 1 webkit-bug-importer 2026-02-09 16:00:28 -0800 <rdar://problem/170008549> 2179651 2 d_delatoba 2026-02-09 16:06:40 -0800 Pull request: https://github.com/WebKit/WebKit/pull/58252 2179652 3 ews-feeder 2026-02-09 16:08:40 -0800 Test gardening commit 307119@main (8275904a69cf): <https://commits.webkit.org/307119@main> Reviewed commits have been landed. Closing PR #58252 and removing active labels. 2179658 4 d_delatoba 2026-02-09 16:23:38 -0800 Pull request: https://github.com/WebKit/WebKit/pull/58254 2179660 5 d_delatoba 2026-02-09 16:24:59 -0800 Looks like the test is flaky because it relies on an auto-generated frame identifier (frame3 or frame4) & this is causing the frame number to vary between runs. I’m going to push a patch that resolves this, please review (assuming this is NOT a webkit issue). 2188518 6 rniwa 2026-03-09 16:17:54 -0700 *** This bug has been marked as a duplicate of bug 296199 ***