both fail on windows bots. A lot of those websocket tests have problems across all platforms.
Who is reponsible to look into? :-)
Do the tests just time out?
websocket/tests/frame-lengths.html is failing on Tiger too:
--- /Volumes/Data/WebKit-BuildSlave/tiger-intel-release/build/layout-test-results/websocket/tests/frame-lengths-expected.txt 2010-02-22 13:20:53.000000000 -0800
+++ /Volumes/Data/WebKit-BuildSlave/tiger-intel-release/build/layout-test-results/websocket/tests/frame-lengths-actual.txt 2010-02-22 13:20:53.000000000 -0800
@@ -1,7 +1,7 @@
+FAIL: Timed out waiting for notifyDone to be called
Test sending and receiving small messages of different lengths.
Should say PASS:
Running the test...
I should file a separate bug for Tiger. But this perma-failure renders the bot useless.
I'm going to address this by increasing DRT timeout.
*** This bug has been marked as a duplicate of bug 36380 ***