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'.
<rdar://problem/82727204>
Marked expectations: https://trac.webkit.org/changeset/282005/webkit
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
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.
It looks like that changed around the time that https://trac.webkit.org/changeset/282007/webkit landed
Maybe these need the "dumpJSConsoleLogInStdErr" treatment?
I added the above in r286577 to see if they are still flaky.
(In reply to Ryan Haddad from comment #7) > I added the above in r286577 to see if they are still flaky. Well, that definitely suppressed the `CONSOLE MESSAGE: Unrecognized Content-Security-Policy directive 'worker-src'.` messages and the test is back to being a flaky failure.
Created attachment 457562 [details] Is this still Flaky on EWS?
These don't seem to be causing EWS issues anymore, I updated expectations and will keep an eye on the bots for the next couple days: Committed: https://trac.webkit.org/changeset/292866/webkit