@jerome, this patches should improve transparency of what is going on. I decided to do this, because I've hit several tests for which nxdtest log output is completely empty even though corresponding test lines are still in Running state. We want to see just from the log whether nxdtest is stuck or whether it exited cleanly and run n test (with n=0 indicating that it had nothing to run).

Please see details and context in the patch1.