37124 2010-04-05 16:07:45 -0700 websocket/tests/handshake-fail-by-sub-protocol-mismatch.html failed on Snow Leopard Release Bot 2011-05-01 17:43:35 -0700 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) PC OS X 10.5 RESOLVED FIXED P2 Normal --- 1 eric webkit-unassigned ukai oldest_to_newest 208769 0 eric 2010-04-05 16:07:45 -0700 websocket/tests/handshake-fail-by-sub-protocol-mismatch.html failed on Snow Leopard Release Bot http://build.webkit.org/results/SnowLeopard%20Intel%20Release%20(Tests)/r57098%20(7704)/websocket/tests/handshake-fail-by-sub-protocol-mismatch-diffs.txt --- /Volumes/Data/WebKit-BuildSlave/snowleopard-intel-release-tests/build/layout-test-results/websocket/tests/handshake-fail-by-sub-protocol-mismatch-expected.txt 2010-04-05 15:53:59.000000000 -0700 +++ /Volumes/Data/WebKit-BuildSlave/snowleopard-intel-release-tests/build/layout-test-results/websocket/tests/handshake-fail-by-sub-protocol-mismatch-actual.txt 2010-04-05 15:53:59.000000000 -0700 @@ -1,8 +1,8 @@ -CONSOLE MESSAGE: line 0: Error during WebSocket handshake: protocol mismatch: requestting-protocol != available-protocol Test WebSocket handshake fail if sub protocol name mismatches. On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE". +Timed out in state: 0 PASS protocol is undefined. PASS successfullyParsed is true I expect this is just a flaky test. http://trac.webkit.org/browser/trunk/LayoutTests/websocket/tests/handshake-fail-by-sub-protocol-mismatch.html 396127 1 eric 2011-05-01 17:43:35 -0700 This is automatically tracked by the cq these days.