Bug 229875 - [ iOS ] imported/w3c/web-platform-tests/content-security-policy/worker-src/service-* tests are consistently failing
Summary: [ iOS ] imported/w3c/web-platform-tests/content-security-policy/worker-src/se...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: WebKit Nightly Build
Hardware: iPhone / iPad Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2021-09-03 09:43 PDT by ayumi_kojima
Modified: 2021-12-06 16:46 PST (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ayumi_kojima 2021-09-03 09:43:21 PDT
imported/w3c/web-platform-tests/content-security-policy/worker-src/service-fallback.https.sub.html
imported/w3c/web-platform-tests/content-security-policy/worker-src/service-list.https.sub.html
imported/w3c/web-platform-tests/content-security-policy/worker-src/service-none.https.sub.html
imported/w3c/web-platform-tests/content-security-policy/worker-src/service-self.https.sub.html

Is a flaky failure on iOS-14-Simulator-WK2-Tests-EWS.

The flaky failure is not seen in the open source directory: https://results.webkit.org/?suite=layout-tests&suite=layout-tests&suite=layout-tests&suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fcontent-security-policy%2Fworker-src%2Fservice-fallback.https.sub.html&test=imported%2Fw3c%2Fweb-platform-tests%2Fcontent-security-policy%2Fworker-src%2Fservice-list.https.sub.html&test=imported%2Fw3c%2Fweb-platform-tests%2Fcontent-security-policy%2Fworker-src%2Fservice-none.https.sub.html&test=imported%2Fw3c%2Fweb-platform-tests%2Fcontent-security-policy%2Fworker-src%2Fservice-self.https.sub.html

It looks like the flaky timeout started at https://ews-build.webkit.org/#/builders/51/builds/17399

Result page: https://ews-build.s3-us-west-2.amazonaws.com/iOS-14-Simulator-WK2-Tests-EWS/r433349-17399-rerun/results.html

Diff: 

--- /Volumes/Data/worker/iOS-14-Simulator-WK2-Tests-EWS/build/layout-test-results/imported/w3c/web-platform-tests/content-security-policy/worker-src/service-fallback.https.sub-expected.txt
+++ /Volumes/Data/worker/iOS-14-Simulator-WK2-Tests-EWS/build/layout-test-results/imported/w3c/web-platform-tests/content-security-policy/worker-src/service-fallback.https.sub-actual.txt
@@ -1,3 +1,5 @@
 
-PASS Same-origin service worker allowed by host-source expression.
+Harness Error (TIMEOUT), message = null
 
+TIMEOUT Same-origin service worker allowed by host-source expression. Test timed out
+

stderr:

CONSOLE MESSAGE: Unrecognized Content-Security-Policy directive 'worker-src'.
Comment 1 Radar WebKit Bug Importer 2021-09-03 09:43:51 PDT
<rdar://problem/82727204>
Comment 2 ayumi_kojima 2021-09-03 09:48:16 PDT
Marked expectations: https://trac.webkit.org/changeset/282005/webkit
Comment 3 ayumi_kojima 2021-09-03 16:10:05 PDT
Apparently, the flaky failure has been showing up in the open source. I was not able to reproduce the failure at TOT using: run-webkit-tests --iterations 500 --exit-after-n-failures 1 --force imported/w3c/web-platform-tests/content-security-policy/worker-src/service-fallback.https.sub.html --ios-simulator
Comment 4 Ryan Haddad 2021-11-30 14:35:09 PST
These test are consistently failing now with the following output:

--- /Volumes/Data/worker/ios-simulator-15-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/content-security-policy/worker-src/service-list.https.sub-expected.txt
+++ /Volumes/Data/worker/ios-simulator-15-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/content-security-policy/worker-src/service-list.https.sub-actual.txt
@@ -1,3 +1,5 @@
+CONSOLE MESSAGE: Unrecognized Content-Security-Policy directive 'worker-src'.
+
 
 PASS Same-origin service worker allowed by host-source expression.
Comment 5 Ryan Haddad 2021-11-30 14:38:13 PST
It looks like that changed around the time that https://trac.webkit.org/changeset/282007/webkit landed
Comment 6 Ryan Haddad 2021-11-30 14:39:09 PST
Maybe these need the "dumpJSConsoleLogInStdErr" treatment?
Comment 7 Ryan Haddad 2021-12-06 16:46:23 PST
I added the above in r286577 to see if they are still flaky.