Bug 83124 - worker-reload.html flakily prints console messages
Summary: worker-reload.html flakily prints console messages
Status: RESOLVED DUPLICATE of bug 83173
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Yuta Kitamura
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-04 01:33 PDT by Yuta Kitamura
Modified: 2012-04-12 03:05 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yuta Kitamura 2012-04-04 01:33:36 PDT 
http/tests/websocket/tests/hybi/workers/worker-reload.html

This test prints the following console messages random number of times on Mac bots:

--- /Volumes/Data/slave/lion-intel-release-tests/build/layout-test-results/http/tests/websocket/tests/hybi/workers/worker-reload-expected.txt
+++ /Volumes/Data/slave/lion-intel-release-tests/build/layout-test-results/http/tests/websocket/tests/hybi/workers/worker-reload-actual.txt
@@ -1,3 +1,21 @@
+CONSOLE MESSAGE: WebSocket network error: The operation couldn’t be completed. Connection refused
+CONSOLE MESSAGE: WebSocket network error: The operation couldn’t be completed. Connection refused
+CONSOLE MESSAGE: WebSocket network error: The operation couldn’t be completed. Connection refused
+CONSOLE MESSAGE: WebSocket network error: The operation couldn’t be completed. Connection refused
+CONSOLE MESSAGE: WebSocket network error: The operation couldn’t be completed. Connection refused
+CONSOLE MESSAGE: WebSocket network error: The operation couldn’t be completed. Connection refused
+CONSOLE MESSAGE: WebSocket network error: The operation couldn’t be completed. Connection refused
+CONSOLE MESSAGE: WebSocket network error: The operation couldn’t be completed. Connection refused
+CONSOLE MESSAGE: WebSocket network error: The operation couldn’t be completed. Connection refused
+CONSOLE MESSAGE: WebSocket network error: The operation couldn’t be completed. Connection refused
+CONSOLE MESSAGE: WebSocket network error: The operation couldn’t be completed. Connection refused
+CONSOLE MESSAGE: WebSocket network error: The operation couldn’t be completed. Connection refused
+CONSOLE MESSAGE: WebSocket network error: The operation couldn’t be completed. Connection refused
+CONSOLE MESSAGE: WebSocket network error: The operation couldn’t be completed. Connection refused
+CONSOLE MESSAGE: WebSocket network error: The operation couldn’t be completed. Connection refused
+CONSOLE MESSAGE: WebSocket network error: The operation couldn’t be completed. Connection refused
+CONSOLE MESSAGE: WebSocket network error: The operation couldn’t be completed. Connection refused
+CONSOLE MESSAGE: WebSocket network error: The operation couldn’t be completed. Connection refused
 Reload after WebSocket creation should not cause a crash.
 
 On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".


On GTK Release bots, the test prints the similar message exactly 100 times (as the test reloads the same page 100 times).

These messages can be safely ignored (this test only checks for crashes), but we need to figure out a way to prevent these messages.
Comment 1 Yuta Kitamura 2012-04-04 18:06:22 PDT 
I will fix this issue in bug 83173.

*** This bug has been marked as a duplicate of bug 83173 ***
Comment 2 Yuta Kitamura 2012-04-12 03:05:59 PDT 
This was fixed.

http://test-results.appspot.com/dashboards/flakiness_dashboard.html#group=%40ToT%20-%20webkit.org&tests=worker-reload.html

I'm going to remove the expectations.