222748 2021-03-04 10:10:03 -0800 [MacOS Debug] http/tests/security/contentSecurityPolicy/frame-src-cross-origin-load.html is a flakey failure 2021-09-17 13:57:52 -0700 1 1 1 Unclassified WebKit New Bugs WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED https://bugs.webkit.org/show_bug.cgi?id=230428 InRadar P2 Normal --- 1 amir_mark webkit-unassigned ayumi_kojima webkit-bot-watchers-bugzilla webkit-bug-importer oldest_to_newest 1735902 0 amir_mark 2021-03-04 10:10:03 -0800 http/tests/security/contentSecurityPolicy/frame-src-cross-origin-load.html This is a flakey failure on both BigSur WK1/Wk2 Debug and Catalina Wk1/Wk2 Debug History: https://results.webkit.org/?suite=layout-tests&test=http%2Ftests%2Fsecurity%2FcontentSecurityPolicy%2Fframe-src-cross-origin-load.html Text DIff: --- /Volumes/Data/worker/bigsur-release-tests-wk1/build/layout-test-results/http/tests/security/contentSecurityPolicy/frame-src-cross-origin-load-expected.txt +++ /Volumes/Data/worker/bigsur-release-tests-wk1/build/layout-test-results/http/tests/security/contentSecurityPolicy/frame-src-cross-origin-load-actual.txt @@ -1,6 +1,6 @@ CONSOLE MESSAGE: Refused to load https://localhost:8443/security/contentSecurityPolicy/resources/alert-fail.html because it does not appear in the frame-src directive of the Content Security Policy. +CONSOLE MESSAGE: PASS ALERT: PASS -CONSOLE MESSAGE: PASS IFrames blocked by CSP should generate a 'load' event, regardless of blocked state. This means they appear to be normal cross-origin loads, thereby not leaking URL information directly to JS. On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE". 1735909 1 webkit-bug-importer 2021-03-04 10:22:05 -0800 <rdar://problem/75044431> 1744978 2 amir_mark 2021-03-29 16:25:33 -0700 Updated test expectations: https://trac.webkit.org/changeset/275191/webkit 1794585 3 ayumi_kojima 2021-09-17 13:41:20 -0700 Seems like the test is no longer failing, but it's timing out instead. I removed the pass/failure expectation and will create a new bug for timeout. https://trac.webkit.org/changeset/282690/webkit 1794590 4 ayumi_kojima 2021-09-17 13:46:20 -0700 My mistake. It is still failing and no timeout. Since I already closed the bug, I will create a new bug.