The test seems to either succeed or timeout.

Sample output:
06:53:51.838 26754 worker/0 http/tests/security/mixedContent/websocket/insecure-websocket-in-secure-page-worker-allowed.html output stderr lines:
06:53:51.838 26754   Xlib:  extension "RANDR" missing on display ":9".
06:53:51.838 26754   Xlib:  extension "RANDR" missing on display ":9".
06:53:51.838 26754   [27175:27395:0314/065345:2789084490:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer with pid 27431: Permission denied
06:53:51.838 26754   [27175:27407:0314/065346:2789348180:ERROR:cert_verify_proc_nss.cc(984)] CERT_PKIXVerifyCert for 127.0.0.1 failed err=-8181
06:53:51.839 26754   [27175:27175:0314/065346:2789383418:WARNING:web_contents_impl.cc(3279)] https://127.0.0.1:8443/ ran insecure content from ws://127.0.0.1:8880/echo
06:53:51.839 26754   [27404:27404:0314/065346:2789453130:ERROR:sandbox_linux.cc(334)] InitializeSandbox() called with multiple threads in process gpu-process
06:53:51.839 26754   [27404:27522:0314/065346:2789456276:WARNING:ipc_message_attachment_set.cc(57)] MessageAttachmentSet destroyed with unconsumed descriptors: 0/1
06:53:51.843 16141 [27/30] http/tests/security/mixedContent/websocket/insecure-websocket-in-secure-page-worker-allowed.html failed unexpectedly (test timed out)
06:53:51.840 26754 worker/0 killing primary driver
06:53:51.842 26754 worker/0 killing secondary driver
06:53:51.842 26754 worker/0 http/tests/security/mixedContent/websocket/insecure-websocket-in-secure-page-worker-allowed.html failed:
06:53:51.842 26754 worker/0  test timed out
06:53:51.842 26754 worker/0 killing secondary driver
06:53:51.843 26754 worker/0 exiting
06:53:51.843 26754 worker/0 cleaning up
06:53:51.843 26754 worker/0 killing primary driver
06:53:51.844 26754 worker/0 killing secondary driver

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/eb3f9a3b6aab20a78445157091ded18cf74728b4

commit eb3f9a3b6aab20a78445157091ded18cf74728b4
Author: csharp <csharp@chromium.org>
Date: Mon Mar 14 18:25:12 2016

Mark http/tests/security/mixedContent/websocket/insecure-websocket-in-secure-page-worker-allowed.html as flaky

TBR=mkwst@chromium.org
BUG= 594595 

Review URL: https://codereview.chromium.org/1796923002

Cr-Commit-Position: refs/heads/master@{#381016}

[modify] https://crrev.com/eb3f9a3b6aab20a78445157091ded18cf74728b4/third_party/WebKit/LayoutTests/TestExpectations

 Issue 430773  has been merged into this issue.

Oops, the test name is different.

 Issue 588535  has been merged into this issue.

Deprecating component:Blink>LayoutTests, to use label Test=Layout instead.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/c8c31351d42c9ed62418ac6fcab6acea74b094db

commit c8c31351d42c9ed62418ac6fcab6acea74b094db
Author: qyearsley <qyearsley@chromium.org>
Date: Thu Sep 29 22:23:14 2016

Run update-test-expectations after making it less conservative.

The change http://crrev.com/2380173002 would make update-test-expectations delete lines as long as the test appears non-flaky on all configurations with existing builders, ignoring configurations with no existing builders.

This CL is the result of running that script -- so for any lines deleted here, that script has found that in recent runs for all existing matching continuous builders, the test appears non-flaky, i.e. passing all recent runs.

BUG=248938, 339597 , 352405 , 364250 , 381730 , 404597 , 410949 , 419696 , 473718 , 498539 , 518915 , 520169 , 520180 , 520183 ,520187, 520191 , 520612 , 520614 , 521084 ,521086, 521090 , 521093 , 521094 , 521099 , 521107 , 521855 , 522645 , 542541 , 552532 , 587593 , 587779 ,588103, 594595 , 594672 , 597572 , 613510 , 614197 , 622672 , 629711 

Review-Url: https://codereview.chromium.org/2384573002
Cr-Commit-Position: refs/heads/master@{#421954}

[modify] https://crrev.com/c8c31351d42c9ed62418ac6fcab6acea74b094db/third_party/WebKit/LayoutTests/TestExpectations