TestWebKitAPI.ParserYieldTokenTests.AsyncScriptRunsWhenFetched is a fairly consistent failure on Monterey and up. It isn't a constant failure, but it fails more than it passes which is why I am calling it consistent. HISTORY: https://results.webkit.org/?suite=api-tests&test=TestWebKitAPI.ParserYieldTokenTests.AsyncScriptRunsWhenFetched FAILURE STDIO: TestWebKitAPI.ParserYieldTokenTests.AsyncScriptRunsWhenFetched /Volumes/Data/worker/Apple-Ventura-Release-Build/build/Tools/TestWebKitAPI/Tests/WebKitCocoa/ParserYieldTokenTests.mm:195 Expected equality of these values: "Running async script." eventMessages[2] Which is: "Finished requesting async script." /Volumes/Data/worker/Apple-Ventura-Release-Build/build/Tools/TestWebKitAPI/Tests/WebKitCocoa/ParserYieldTokenTests.mm:196 Expected equality of these values: "Finished requesting async script." eventMessages[3] Which is: "Running async script."
<rdar://problem/109173614>
I have reproduce the failure on Ventura Release ToT running as follows: run-api-tests --no-build --release --verbose TestWebKitAPI.ParserYieldTokenTests.AsyncScriptRunsWhenFetched I was also able to bisect to a specific regression point. This fails at 263724@main, but not at 263723@main. So it appears that https://commits.webkit.org/263724@main is the culprit here.
I don't know how this test was able to stay consistent until now. There is no basis that guarantees "Running async script" to happen before "Finished requesting async script".
Pull request: https://github.com/WebKit/WebKit/pull/13735
Committed 263948@main (360db466f1b5): <https://commits.webkit.org/263948@main> Reviewed commits have been landed. Closing PR #13735 and removing active labels.