Once run, pool_test.py permanently turns on output of irods.connection logger at a DEBUG level. To be balanced, it should turn that logger off again.
Alone this mightn't have been a problem, but because of propagation being set to True by default, the RootLogger streamhandler, which outputs Everything passing over the socket to the iRODS server, for each test running after the pool_test.
Once run, pool_test.py permanently turns on output of irods.connection logger at a DEBUG level. To be balanced, it should turn that logger off again.
Alone this mightn't have been a problem, but because of
propagationbeing set toTrueby default, the RootLogger streamhandler, which outputs Everything passing over the socket to the iRODS server, for each test running after the pool_test.