RESOLVED FIXED 53816
Flaky Test: http/tests/websocket/tests/handshake-fail-by-maxlength.html 
https://bugs.webkit.org/show_bug.cgi?id=53816
Summary Flaky Test: http/tests/websocket/tests/handshake-fail-by-maxlength.html
WebKit Commit Bot
Reported 2011-02-04 15:00:49 PST
This is an automatically generated bug from the commit-queue. http/tests/websocket/tests/handshake-fail-by-maxlength.html has been flaky on the commit-queue. http/tests/websocket/tests/handshake-fail-by-maxlength.html was authored by . http://trac.webkit.org/browser/trunk/LayoutTests/http/tests/websocket/tests/handshake-fail-by-maxlength.html The commit-queue just saw http/tests/websocket/tests/handshake-fail-by-maxlength.html flake (Text diff mismatch) while processing attachment 81272 [details] on bug 50773. Bot: cr-jail-8 Port: Mac Platform: Mac OS X 10.6.6 The bots will update this with information from each new failure. If you believe this bug to be fixed or invalid, feel free to close. The bots will re-open if the flake re-occurs. If you would like to track this test fix with another bug, please close this bug as a duplicate. The bots will follow the duplicate chain when making future comments.
Attachments
Failure diff from cr-jail-8 (727 bytes, text/plain)
2011-02-04 15:00 PST, WebKit Commit Bot 		no flags
Details
Failure diff from eseidel-cq-sf (727 bytes, text/plain)
2011-04-11 13:53 PDT, WebKit Commit Bot 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
WebKit Commit Bot
Comment 1 2011-02-04 15:00:52 PST
Created attachment 81296 [details] Failure diff from cr-jail-8
WebKit Commit Bot
Comment 2 2011-04-11 13:53:15 PDT
The commit-queue just saw http/tests/websocket/tests/handshake-fail-by-maxlength.html flake (Text diff mismatch) while processing attachment 89016 [details] on bug 58241. Bot: eseidel-cq-sf Port: Mac Platform: Mac OS X 10.6.4
WebKit Commit Bot
Comment 3 2011-04-11 13:53:17 PDT
Created attachment 89077 [details] Failure diff from eseidel-cq-sf
Eric Seidel (no email)
Comment 4 2011-05-01 17:46:55 PDT
Adam moved the websocket tests over to a real http server and most of the flakiness went away. If you see this again, please re-open.
Note You need to log in before you can comment on or make changes to this bug.