Bug 232774 - Regression(r284472) http/tests/security/mixedContent/websocket/insecure-websocket-in-iframe.html is flaky
Summary: Regression(r284472) http/tests/security/mixedContent/websocket/insecure-webso...
Status: RESOLVED DUPLICATE of bug 232810
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Chris Dumez
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2021-11-05 17:05 PDT by Chris Dumez
Modified: 2021-11-08 07:20 PST (History)
3 users (show)

See Also:


Attachments
Patch (1.79 KB, patch)
2021-11-05 17:08 PDT, Chris Dumez
ews-feeder: commit-queue-
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Dumez 2021-11-05 17:05:42 PDT
http/tests/security/mixedContent/websocket/insecure-websocket-in-iframe.html is flaky:

Diff:
--- /Volumes/Data/worker/debug-wk2-tests/build/OpenSource/layout-test-results/http/tests/security/mixedContent/websocket/insecure-websocket-in-iframe-expected.txt
+++ /Volumes/Data/worker/debug-wk2-tests/build/OpenSource/layout-test-results/http/tests/security/mixedContent/websocket/insecure-websocket-in-iframe-actual.txt
@@ -2,7 +2,6 @@
 
 CONSOLE MESSAGE: WebSocket connection failed.
 CONSOLE MESSAGE: WebSocket connection failed: WebSocket is closed before the connection is established.
-CONSOLE MESSAGE: WebSocket closed.
 This test loads an iframe that creates an insecure WebSocket connection. We should block the connection and trigger a mixed content callback because the main frame is HTTPS, but the data sent over the socket could be recorded or controlled by an attacker.
Comment 1 Chris Dumez 2021-11-05 17:06:09 PDT
<rdar://84997169>
Comment 2 Chris Dumez 2021-11-05 17:08:47 PDT
Created attachment 443458 [details]
Patch
Comment 3 Chris Dumez 2021-11-08 07:20:38 PST

*** This bug has been marked as a duplicate of bug 232810 ***