Bug 33279

Summary: fast/websockets/websocket-event-target.html causes any test after it to fail
Product: WebKit Reporter: Eric Seidel (no email) <eric>
Component: Tools / TestsAssignee: Alexey Proskuryakov <ap>
Status: RESOLVED FIXED    
Severity: Normal CC: abecsi, ap, ukai
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: OS X 10.5   
Attachments:
Description Flags
fix the test eric: review+

Description Eric Seidel (no email) 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.
Comment 1 Eric Seidel (no email) 2010-01-06 17:08:39 PST 
*** Bug 33256 has been marked as a duplicate of this bug. ***
Comment 2 Alexey Proskuryakov 2010-01-06 17:17:53 PST 
Eric, do you know when this started? I'm fairly sure this test was good originally.
Comment 3 Eric Seidel (no email) 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?
Comment 4 Alexey Proskuryakov 2010-01-08 15:48:48 PST 
Created attachment 46169 [details]
fix the test
Comment 5 Eric Seidel (no email) 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!
Comment 6 Alexey Proskuryakov 2010-01-08 16:04:16 PST 
Committed <http://trac.webkit.org/changeset/53019>.