http/tests/security/contentSecurityPolicy/script-src-parsing-implicit-and-explicit-port-number.html is a flaky text failure on macOS wk1 and EWS. HISTORY: https://results.webkit.org/?suite=layout-tests&test=http%2Ftests%2Fsecurity%2FcontentSecurityPolicy%2Fscript-src-parsing-implicit-and-explicit-port-number.html TEXT DIFF: --- /Volumes/Data/worker/Apple-Ventura-Debug-WK1-Tests/build/layout-test-results/http/tests/security/contentSecurityPolicy/script-src-parsing-implicit-and-explicit-port-number-expected.txt +++ /Volumes/Data/worker/Apple-Ventura-Debug-WK1-Tests/build/layout-test-results/http/tests/security/contentSecurityPolicy/script-src-parsing-implicit-and-explicit-port-number-actual.txt @@ -1,3 +1,4 @@ +CONSOLE MESSAGE: Blocked https://127.0.0.1:8443/security/contentSecurityPolicy/resources/script.js from asking for credentials because it is a cross-origin request. Tests script-src source expression matching with implicit and explicit default port numbers. DIFF URL: https://build.webkit.org/results/Apple-Ventura-Debug-WK1-Tests/257133@main%20(301)/http/tests/security/contentSecurityPolicy/script-src-parsing-implicit-and-explicit-port-number-pretty-diff.html
<rdar://problem/102785446>
Test gardening commit 257143@main (265eb3e3a404): <https://commits.webkit.org/257143@main> Reviewed commits have been landed. Closing PR #6942 and removing active labels.
The rebase above has resoled the issue. Closing.
(In reply to Robert Jenner from comment #3) > The rebase above has resoled the issue. Closing. This comment is actually an error. This bug was not a rebase, and is still under investigation.
This is likely caused by https://commits.webkit.org/256173@main. Similar logging was addressed after this patch via rebase lines or adding the [ DumpJSConsoleLogInStdErr ] annotation.
Pull request: https://github.com/WebKit/WebKit/pull/9017
Test gardening commit 259263@main (64f4051a7f07): <https://commits.webkit.org/259263@main> Reviewed commits have been landed. Closing PR #9017 and removing active labels.