Bug 73666 – [GTK] http/tests/websocket/tests/hybi/bufferedAmount-after-close-in-busy.html fails

• Status: RESOLVED
• Resolution: FIXED
• Component: WebKitGTK

[Philippe Normand]

--- /var/lib/buildbot/build/gtk-linux-32-release/build/layout-test-results/http/tests/websocket/tests/hybi/bufferedAmount-after-close-in-busy-expected.txt 
+++ /var/lib/buildbot/build/gtk-linux-32-release/build/layout-test-results/http/tests/websocket/tests/hybi/bufferedAmount-after-close-in-busy-actual.txt 
@@ -1,3 +1,4 @@
+CONSOLE MESSAGE: line 0: WebSocket network error: error code 0
 Web Socket bufferedAmount after closed in busy
 
 On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".

Not sure what to do here. Any hint? Takashi?

[Takashi Toyoshima]

Thank you for letting me know.

This new test closes WebSocket connection when sending buffer is not empty.
In this situation, platformSend will be called after connection start to close, or is in CLOSING state.
I think this console message is related to the case.
I'll investigate it.

[Takashi Toyoshima]

Created attachment 118345 [details]
Patch

[Takashi Toyoshima]

Sorry, the reason was in my test.
Server side handler began server initiated closing handshake unexpectedly.

Anyway, current SocketStreamHandlerError doesn't contain message to show in log.
I'll also post a patch to improve it soon.

Thanks

[Kent Tamura]

Comment on attachment 118345 [details]
Patch

ok

[WebKit Review Bot]

Comment on attachment 118345 [details]
Patch

Clearing flags on attachment: 118345

Committed r102327: <http://trac.webkit.org/changeset/102327>

[WebKit Review Bot]

All reviewed patches have been landed.  Closing bug.