On Mon, Dec 2, 2013 at 12:17 PM, Andrew Clegg <andrew.clegg+paral...@gmail.com> wrote:
> Alternatively, maybe some sort of a --fail-fast flag, which will cause > the whole thing to abort (with a message to stderr) if one of the jobs > returns non-zero? Please elaborate how --fail-fast would differ from --halt-on-error. > This might be generally useful for long-running jobs, especially in > the cases like this where it's a common failure mode that would mean > you need to restart them all anyway. For long running jobs you would normally use --joblog/--results + --resume. /Ole
