Now that the server starts properly when run from within /tmp I’ve noticed that three of the four WebSocket tests fail in this situation. The results indicate that the tests were not able to contact the server. The tests pass on the same machine if I use a source tree placed on my desktop. We shouldn’t have tests that fail when run from a different place on disk.
I don't know if this is an issue anymore, but it's so far in the past I'm just going to close it. If we can reproduce this on a recent system, lets open a new bug.