websocket/tests/long-invalid-header.html inroduced in http://trac.webkit.org/changeset/56380. It fails on Qt bots because of different CONSOLE MESSAGE, but the PASS and TEST COMPLETE is correct and it passes in QtLauncher http://build.webkit.org/results/Qt%20Linux%20Release/r56386%20%288922%29/websocket/tests/long-invalid-header-pretty-diff.html http://www.sed.hu/webkit/qtbuildbot/results/x86-32%20Linux%20Qt%20Debug/r56386%20%281395%29/websocket/tests/long-invalid-header-pretty-diff.html I think the it might be a Qt-DRT bug.
websocket/tests/long-invalid-header.html skipped to make bots happy: http://trac.webkit.org/changeset/56389
I think the expected data depends on how data is buffered/delivered from SocketStreamHandle to WebSocketChannel,WebSocketHandshake. I think console message doesn't need to whole data in buffer.
Created attachment 51479 [details] Patch
Comment on attachment 51479 [details] Patch I'm surprised this wouldn't be a part of the Console classes instead of done ad-hoc for WebSocket here. But this is OK for now I guess.
CCing inspector gurus.
Committed r56511: <http://trac.webkit.org/changeset/56511>