Comment 3 for bug 526353

Revision history for this message
Vincent Ladeuil (vila) wrote :

So, this failure is related to the thread/socket leaks in the tests (i.e. purely a test infrastructure problem,
bzr itself is not concerned).

As mentioned in bug #392127, a workaround is to run with --parallel=fork which
allows the test suite to complete without any errors (I'm running it this way every day in a VM with 4 cores).

If you don't have a multi-core processor, you can use BZR_CONCURRENCY=n to force it.

Add your new comments to bug #392127 or bug #392402, thanks in advance.