The following layout test is failing on Win10 http/tests/websocket/tests/hybi/non-document-mixed-content-blocked-https-with-embedded-http-with-embedded-https.https.html Probable cause: This started with the build: https://build.webkit.org/builders/Apple%20Win%2010%20Release%20(Tests)/builds/3635 Flakiness Dashboard: https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=http%2Ftests%2Fwebsocket%2Ftests%2Fhybi%2Fnon-document-mixed-content-blocked-https-with-embedded-http-with-embedded-https.https.html Diff: --- /home/buildbot/worker/win10-release-tests/build/layout-test-results/http/tests/websocket/tests/hybi/non-document-mixed-content-blocked-https-with-embedded-http-with-embedded-https.https-expected.txt +++ /home/buildbot/worker/win10-release-tests/build/layout-test-results/http/tests/websocket/tests/hybi/non-document-mixed-content-blocked-https-with-embedded-http-with-embedded-https.https-actual.txt @@ -1,6 +1,6 @@ CONSOLE MESSAGE: The page at about:blank was allowed to display insecure content from http://localhost:8000/websocket/tests/hybi/non-document-mixed-content-blocked-http-with-embedded-https.html. -CONSOLE MESSAGE: WebSocket connection failed: The page at https://localhost:8443/websocket/tests/hybi/non-document-mixed-content-blocked.https.html was blocked from connecting insecurely to ws://127.0.0.1:8880/websocket/tests/hybi/simple either because the protocol is insecure or the page is embedded from an insecure page. +FAIL: Timed out waiting for notifyDone to be called Test topFrame https with embedded http with embedded https blocks worker trying to connect with insecure webSocket.
<rdar://problem/56262297>
Marked this test as failing as part of: https://trac.webkit.org/changeset/251098/webkit