So it turns out this bug is really about SocketServer objects that are *not* intended to be used with a client
*thread* in the same process.
While I've made significant progress in reducing both the number of leaking tests and the threads left around
by a full test suite run, I now experiment a new kind of hang on FreeBSD and OSX.
I can't therefore release such a fix without digging further :-/
The status is that using '--parallel=fork' to run the full test suite is the only way to make it pass on all
platforms known to our test botnet (babune).
So it turns out this bug is really about SocketServer objects that are *not* intended to be used with a client
*thread* in the same process.
While I've made significant progress in reducing both the number of leaking tests and the threads left around
by a full test suite run, I now experiment a new kind of hang on FreeBSD and OSX.
I can't therefore release such a fix without digging further :-/
The status is that using '--parallel=fork' to run the full test suite is the only way to make it pass on all
platforms known to our test botnet (babune).