[iOS] Layout test imported/w3c/web-platform-tests/service-workers/service-worker/fetch-mixed-content-to-inscope.https.html and fetch-mixed-content-to-outscope.https.html are flaky failures Both tests are flaky when run on iOS 12. The diffs show that they are hitting a harness timeout: --- /build/layout-test-results/imported/w3c/web-platform-tests/service-workers/service-worker/fetch-mixed-content-to-inscope.https-expected.txt +++ /build/layout-test-results/imported/w3c/web-platform-tests/service-workers/service-worker/fetch-mixed-content-to-inscope.https-actual.txt @@ -1,8 +1,8 @@ -CONSOLE MESSAGE: FetchEvent.respondWith received an error: TypeError: Not allowed to request resource -CONSOLE MESSAGE: Cannot load https://localhost:9443/service-workers/service-worker/resources/dummy?mode=no-cors&url=http%3A%2F%2Flocalhost%3A8800%2Fservice-workers%2Fservice-worker%2Fresources%2Ffetch-access-control.py%3FPNGIMAGE. -CONSOLE MESSAGE: FetchEvent.respondWith received an error: TypeError: Not allowed to request resource -CONSOLE MESSAGE: Cannot load https://localhost:9443/service-workers/service-worker/resources/dummy?mode=no-cors&url=http%3A%2F%2F127.0.0.1%3A8800%2Fservice-workers%2Fservice-worker%2Fresources%2Ffetch-access-control.py%3FPNGIMAGE. +CONSOLE MESSAGE: FetchEvent.respondWith received an error: TypeError: An SSL error has occurred and a secure connection to the server cannot be made. +CONSOLE MESSAGE: Cannot load https://localhost:9443/service-workers/service-worker/resources/fetch-mixed-content-iframe-inscope-to-inscope.html. -PASS Verify Mixed content of fetch() in a Service Worker +Harness Error (TIMEOUT), message = null +TIMEOUT Verify Mixed content of fetch() in a Service Worker Test timed out + --- /build/layout-test-results/imported/w3c/web-platform-tests/service-workers/service-worker/fetch-mixed-content-to-outscope.https-expected.txt +++ /build/layout-test-results/imported/w3c/web-platform-tests/service-workers/service-worker/fetch-mixed-content-to-outscope.https-actual.txt @@ -1,12 +1,8 @@ -CONSOLE MESSAGE: line 25: The page at https://localhost:9443/service-workers/service-worker/fetch-mixed-content-to-outscope.https.html was allowed to display insecure content from http://localhost:8800/service-workers/service-worker/resources/fetch-access-control.py?PNGIMAGE. - -CONSOLE MESSAGE: FetchEvent.respondWith received an error: TypeError: Not allowed to request resource -CONSOLE MESSAGE: Cannot load http://localhost:8800/service-workers/service-worker/resources/fetch-access-control.py?PNGIMAGE. -CONSOLE MESSAGE: line 42: The page at https://localhost:9443/service-workers/service-worker/fetch-mixed-content-to-outscope.https.html was allowed to display insecure content from http://127.0.0.1:8800/service-workers/service-worker/resources/fetch-access-control.py?PNGIMAGE. - -CONSOLE MESSAGE: FetchEvent.respondWith received an error: TypeError: Not allowed to request resource -CONSOLE MESSAGE: Cannot load http://127.0.0.1:8800/service-workers/service-worker/resources/fetch-access-control.py?PNGIMAGE. +CONSOLE MESSAGE: FetchEvent.respondWith received an error: TypeError: An SSL error has occurred and a secure connection to the server cannot be made. +CONSOLE MESSAGE: Cannot load https://localhost:9443/service-workers/service-worker/resources/fetch-mixed-content-iframe-inscope-to-outscope.html. -PASS Verify Mixed content of fetch() in a Service Worker +Harness Error (TIMEOUT), message = null +TIMEOUT Verify Mixed content of fetch() in a Service Worker Test timed out +
Marked tests as flaky in https://trac.webkit.org/changeset/236159/webkit
<rdar://problem/44585050>