RESOLVED DUPLICATE of bug 36380 35041
REGRESSION: websocket/tests/frame-lengths.html / websocket/tests/simple-stress.html fail on Windows bot 
https://bugs.webkit.org/show_bug.cgi?id=35041
Summary REGRESSION: websocket/tests/frame-lengths.html / websocket/tests/simple-stres...
Nikolas Zimmermann
Reported 2010-02-17 07:40:46 PST
websocket/tests/simple-stress.html websocket/tests/frame-lengths.html both fail on windows bots. A lot of those websocket tests have problems across all platforms. Who is reponsible to look into? :-)
Attachments
Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2010-02-17 14:03:26 PST
Do the tests just time out?
Eric Seidel (no email)
Comment 2 2010-02-22 16:48:37 PST
websocket/tests/frame-lengths.html is failing on Tiger too: http://build.webkit.org/results/Tiger%20Intel%20Release/r55101%20(9004)/websocket/tests/frame-lengths-diffs.txt --- /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... -PASS
Eric Seidel (no email)
Comment 3 2010-03-19 12:03:48 PDT
I should file a separate bug for Tiger. But this perma-failure renders the bot useless.
Alexey Proskuryakov
Comment 4 2010-03-19 13:20:48 PDT
I'm going to address this by increasing DRT timeout. *** This bug has been marked as a duplicate of bug 36380 ***
Note You need to log in before you can comment on or make changes to this bug.