[webkit-dev] Please kill old pywebsocket process if you see WebSocket test failures
yutak at chromium.org
Mon May 30 01:57:46 PDT 2011
If the following two tests are failing, it's probably because an old
pywebsocket process is still alive and preventing the new one from starting:
You can observe the following traceback in the layout test output:
Traceback (most recent call last):
File "Tools/Scripts/new-run-webkit-websocketserver", line 108, in
File "Tools/Scripts/new-run-webkit-websocketserver", line 103, in main
line 220, in start
Failed to start PyWebSocket server on port 8880.
If this happens, please kill the old pywebsocket process, or reboot the
*Dear WebKit buildbot administrators:*
A couple of buildbot slaves are affected by this issue (as far as I know).
- apple-macpro-4 (
- apple-xserve-7 (
Could you kill old pywebsocket processes in these bots? After killing them,
the above two tests should start to pass.
*Dear webkitpy hackers:*
run-webkit-websocketserver probably should check if there's any existing
WebSocket server running, and kill it before starting the new one.
However, as I don't know very much about how run-webkit-websocketserver
works, I don't know if this is feasible or not. Do you think this is a good
idea? Is it easily implementable?
Sorry for all the mess, and thank you for your cooperation.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev