Bug 237603 – [ iOS ] 2 imported/w3c/web-platform-tests/content-security-policy/connect-src/* tests are flaky text failures

• Component: Page Loading
• Status: NEW

[Dawn Morningstar]

imported/w3c/web-platform-tests/content-security-policy/connect-src/shared-worker-connect-src-allowed.sub.html
imported/w3c/web-platform-tests/content-security-policy/connect-src/shared-worker-connect-src-blocked.sub.html 
are both flaky text failures on iOS queues. 

Regression may be around r289514. Further investigation is required.

HISTORY:
https://results.webkit.org/?suite=layout-tests&suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fcontent-security-policy%2Fconnect-src%2Fshared-worker-connect-src-allowed.sub.html&test=imported%2Fw3c%2Fweb-platform-tests%2Fcontent-security-policy%2Fconnect-src%2Fshared-worker-connect-src-blocked.sub.html&platform=ios

imported/w3c/web-platform-tests/content-security-policy/connect-src/shared-worker-connect-src-allowed.sub.html
DIFF:
--- /Volumes/Data/worker/ipados-simulator-15-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/content-security-policy/connect-src/shared-worker-connect-src-allowed.sub-expected.txt
+++ /Volumes/Data/worker/ipados-simulator-15-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/content-security-policy/connect-src/shared-worker-connect-src-allowed.sub-actual.txt
@@ -1,3 +1,3 @@
 
-FAIL Expecting logs: ["xhr allowed","TEST COMPLETE"] assert_unreached: unexpected log: xhr blocked Reached unreachable code
+FAIL Expecting logs: ["xhr allowed","TEST COMPLETE"] assert_unreached: Logging timeout, expected logs xhr allowed,TEST COMPLETE not sent. Reached unreachable code
 
DIFF-URL:
https://build.webkit.org/results/Apple-iPadOS-15-Simulator-Release-WK2-Tests/r290762%20(1185)/imported/w3c/web-platform-tests/content-security-policy/connect-src/shared-worker-connect-src-allowed.sub-diff.txt



imported/w3c/web-platform-tests/content-security-policy/connect-src/shared-worker-connect-src-blocked.sub.html 
DIFF:
--- /Volumes/Data/worker/ipados-simulator-15-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/content-security-policy/connect-src/shared-worker-connect-src-blocked.sub-expected.txt
+++ /Volumes/Data/worker/ipados-simulator-15-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/content-security-policy/connect-src/shared-worker-connect-src-blocked.sub-actual.txt
@@ -1,5 +1,5 @@
 This test loads a shared worker, delivered with its own policy. The worker should be blocked from making an XHR as that policy specifies a connect-src 'none', though this resource's policy is connect-src *. No report should be sent since the worker's policy doesn't specify a report-uri.
 
 
-PASS Expecting logs: ["xhr blocked","TEST COMPLETE"]
+FAIL Expecting logs: ["xhr blocked","TEST COMPLETE"] assert_unreached: Logging timeout, expected logs xhr blocked,TEST COMPLETE not sent. Reached unreachable code
 
DIFF-URL:
https://build.webkit.org/results/Apple-iPadOS-15-Simulator-Release-WK2-Tests/r290762%20(1185)/imported/w3c/web-platform-tests/content-security-policy/connect-src/shared-worker-connect-src-blocked.sub-diff.txt

[Radar WebKit Bug Importer]

<rdar://problem/89965072>

[Dawn Morningstar]

marking expectations until further investigation can occur.

[Dawn Morningstar]

Expectations updated with r291059

[Ryan Haddad]

Based on commits that landed shortly before the first failure, https://commits.webkit.org/247042@main seems like it could be related as it was about the SharedWorker process on iOS.

[Chris Dumez]

(In reply to Ryan Haddad from comment #4)
> Based on commits that landed shortly before the first failure,
> https://commits.webkit.org/247042@main seems like it could be related as it
> was about the SharedWorker process on iOS.

Flaky timeouts could indeed indicate that we're failing to take a process assertion on iOS. I can investigate.

[Chris Dumez]

(In reply to Chris Dumez from comment #5)
> (In reply to Ryan Haddad from comment #4)
> > Based on commits that landed shortly before the first failure,
> > https://commits.webkit.org/247042@main seems like it could be related as it
> > was about the SharedWorker process on iOS.
> 
> Flaky timeouts could indeed indicate that we're failing to take a process
> assertion on iOS. I can investigate.

I haven't been able to reproduce so far, even by forcing the shared worker into its own separate process (which is more likely to trigger process suspension).