Andrew Dunstan <andrew@dunslane.net> writes:
> * There is a new config parameter "wait_timeout", which defaults to
> undefined. If it is set then any run that takes longer than the
> specified number of seconds is aborted. That means that runs that
> get stuck will time out, and the whole animal won't be stuck and
> requiring manual intervention. My test animal has a setting of 3 *
> 3600, i.e. 3 hours. There is some possible danger in this, that we
> might miss bugs that cause us to get stuck, so at least some animals
> should not use this feature.
Hm, do you mean that if the timeout is exceeded, it just shuts down and
doesn't report the failure? If there is a report I don't see how we'd
"miss" anything.
regards, tom lane
