I would recommend running with (export ZOPEN_NUM_JOBS=1; zopen build)
Testing can't be turned on by default because it hangs at
the end waiting because there are open sockets from some
failing tests.
If you run it by hand, it will run through all the tests and print the results, but the unit test framework process will hang.
If you then look at the state of the processes, you will see there are a number of open sockets.
To force finish the build, you can kill -9 the python unit test process.
Approaches one could take:
figure out why the sockets are staying open - the testcase output will tell you which they are
then 'skip' those tests
or 'fix' the bug(s) causing those sockets to stay open (assuming they are bugs)
figure out how to fix the unittest framework or add something to the tests themselves to clean up better
To enable tests to be run: Add:
I would recommend running with (export ZOPEN_NUM_JOBS=1; zopen build)
Testing can't be turned on by default because it hangs at the end waiting because there are open sockets from some failing tests.
If you run it by hand, it will run through all the tests and print the results, but the unit test framework process will hang.
If you then look at the state of the processes, you will see there are a number of open sockets. To force finish the build, you can
kill -9
the python unit test process.Approaches one could take: