Program continues after setup fails

[PGijsbers]

In docker mode, I have encountered scenarios where building the image failed, and the benchmark tries to continue invoking the run command. I suspect that it is because config.yaml:setup.activity_timeout seconds elapse during setup without any output, the setup is aborted and this is not handled properly, but it needs some more investigation.

Desired outcome: benchmark stops providing a clear error message that the experiment is aborted due to inactivity in the setup.