W3C home > Mailing lists > Public > public-webapps-testsuite@w3.org > March 2013

Re: [websocket-test] What's the plan for reviewing and approving Opera's WebSocket tests?

From: Michael[tm] Smith <mike@w3.org>
Date: Tue, 5 Mar 2013 11:54:56 +0900
To: Ken Reed <kenre@microsoft.com>
Cc: James Graham <jgraham@opera.com>, "public-webapps-testsuite@w3.org" <public-webapps-testsuite@w3.org>
Message-ID: <20130305025450.GF16125@sideshowbarker>
So I'm seeing an error in the logs that I suspect must be the cause of the
test failures:

  "mod_pywebsocket: web_socket_transfer_data raised exception for /ws/echo: Connection read error"

The full error message is this attached.

I'm trying to troubleshoot it now. I'll let you all know if I make any
progress.

  --Mike

Ken Reed <kenre@microsoft.com>, 2013-03-04 21:14 +0000:

> My ping time to the Internet is consistently sub-10ms. I don't think my environment is contributing undo latency. 
> 
> A quick look at our tracing across a few of these cases which are timing out shows the request is getting to the server but the test is failing due to the server not responding. I have not done a careful survey but it does seem like the passing test might be just the invalid scenarios which wouldn't actually need to hit the server. 
> 
> Sorry, I don't have cycles to debug further. Hopefully these observations suggest some direction for you to investigate...
> 
> On Mon, 4 Mar 2013, Ken Reed wrote:
> 
> > James, are you looking into root causing these Timeout issues?
> >
> > I'm consistently getting Timeout across IE, Chrome, Firefox, and Opera. 
> > If it helps at all, the behavior I'm seeing doesn't seem to be 
> > consistent with something actually timing out. I'm getting the timeout 
> > response back within around three seconds of launching the test. There 
> > are plenty of other tests which take longer than that but do complete.
> 
> I don't know what to do, really. For me all the tests seem to work as expected. For Mike, the timeouts seemed to be explained by his network connection which showed periodic high latencies to w3c-test.org.
> 
> You said that some tests work for you. Do any of these actually require a websocket connection (such a test would have something like var ws = new WebSocket(SCHEME_HOST_PORT + "/ws/foo") in the source)? A number of the tests don't have any actual server-side requirement. Does adding ?wss to the url make a difference? That will use encrypted websockets over port
> 443 instead of websockets in the clear over port 80. How does your latency to w3c-test.org look?
> 
> 

-- 
Michael[tm] Smith http://people.w3.org/mike


Received on Tuesday, 5 March 2013 02:55:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 5 March 2013 02:55:12 GMT