08:12:19 [INFO] entering GooseAttack phase: Starting
08:12:19 [INFO] launching user 1 from AnonBrowsingUser...
08:12:19 [INFO] launching user 2 from AnonBrowsingUser...
08:12:20 [INFO] launching user 3 from AnonBrowsingUser...
08:12:20 [INFO] launching user 4 from AuthBrowsingUser...
08:12:21 [INFO] launching user 5 from AnonBrowsingUser...
08:12:21 [INFO] launching user 6 from AnonBrowsingUser...
08:12:22 [INFO] launching user 7 from AnonBrowsingUser...
08:12:22 [INFO] launching user 8 from AnonBrowsingUser...
08:12:23 [INFO] launching user 9 from AuthBrowsingUser...
08:12:24 [INFO] launching user 10 from AnonBrowsingUser...
08:12:24 [INFO] launched 10 users...
But the AuthBrowsingUser with the delay fails to stop when the load test completes:
08:12:24 [INFO] entering GooseAttack phase: Running
08:12:29 [INFO] entering GooseAttack phase: Stopping
08:12:29 [INFO] stopping after 5 seconds...
08:12:29 [INFO] waiting for users to exit
08:12:29 [INFO] exiting user 7 from AnonBrowsingUser...
08:12:29 [INFO] exiting user 6 from AnonBrowsingUser...
08:12:29 [INFO] exiting user 3 from AnonBrowsingUser...
08:12:29 [INFO] exiting user 8 from AnonBrowsingUser...
08:12:29 [INFO] exiting user 5 from AnonBrowsingUser...
08:12:29 [INFO] exiting user 10 from AnonBrowsingUser...
08:12:29 [INFO] exiting user 2 from AnonBrowsingUser...
08:12:32 [INFO] exiting user 1 from AnonBrowsingUser...
^C08:12:57 [WARN] caught ctrl-c, stopping...
^C08:13:01 [WARN] caught another ctrl-c, exiting immediately...
(And if instead we edit AnonBrowsingUser then all of its threads instead fail to shut down ...)
It seems if you enable a delay of greater than 1s between tasks, shutdown hangs indefinitely. If the delay is <1000ms it doesn't hang.
For example, with the following edit the
drupal_memcache
example hangs on shutdown:If run as follows:
It starts and runs correctly:
But the
AuthBrowsingUser
with the delay fails to stop when the load test completes:(And if instead we edit
AnonBrowsingUser
then all of its threads instead fail to shut down ...)