RESOLVED FIXED 33279
fast/websockets/websocket-event-target.html causes any test after it to fail
https://bugs.webkit.org/show_bug.cgi?id=33279
Summary fast/websockets/websocket-event-target.html causes any test after it to fail
Eric Seidel (no email)
Reported 2010-01-06 17:08:18 PST
fast/websockets/websocket-event-target.html causes any test after it to fail It logs: +CONSOLE MESSAGE: line 0: Unexpected response code:HTML after the test has finished, so the next test after it fails. fast/websockets/websocket-event-target.html was skipped in: http://trac.webkit.org/changeset/52883 See bug 33256 for more information about the failure. Alexey asked that I file a new bug, as bug 33256 got rather long in trying to figure out what was going wrong.
Attachments
fix the test (1.93 KB, patch)
2010-01-08 15:48 PST, Alexey Proskuryakov
eric: review+
Eric Seidel (no email)
Comment 1 2010-01-06 17:08:39 PST
*** Bug 33256 has been marked as a duplicate of this bug. ***
Alexey Proskuryakov
Comment 2 2010-01-06 17:17:53 PST
Eric, do you know when this started? I'm fairly sure this test was good originally.
Eric Seidel (no email)
Comment 3 2010-01-06 17:20:21 PST
The failure occurred on the buildbots this afternoon for builds of revisions between http://trac.webkit.org/changeset/52854 and http://trac.webkit.org/changeset/52877. I suspect that some subtle timing thing was happening on the bots. It's also possible that the bots were under load and thus the python websocket process was running slower?
Alexey Proskuryakov
Comment 4 2010-01-08 15:48:48 PST
Created attachment 46169 [details] fix the test
Eric Seidel (no email)
Comment 5 2010-01-08 15:50:59 PST
Comment on attachment 46169 [details] fix the test Seems we also need to fix DRT, but that can be a separate issue we fight later. Thanks!
Alexey Proskuryakov
Comment 6 2010-01-08 16:04:16 PST
Note You need to log in before you can comment on or make changes to this bug.