I have an atExit function registered, that cleans up data that was created/generated during the run.

The odd behaviour can be seen below, captured with a simply loop outside the run for observation (1 sec interval) to check the state of workers while a test was running. It seams that once test runner exits, the state of status of t

the agents's workers are 'cleared' (which was my indication that things were really done). Grinder also issues a termination at 10 seconds as well, regrettably.

As can been seen, the agent workers look like their state went from running to nothing and then back to finished. Time between this is 30 seconds. Threads are still up during this period, as the cleanup is still being processed.

Is there any efficient way to determine successfully that the workers have passed the 'finished' state? I can't really rely on polling for a state of finished, as there is a chance that it will be missed (it is cleared).