[Buildbot-devel] two timeout settings?

Chris AtLee chris at atlee.ca
Wed Jan 12 18:20:08 UTC 2011

On Wed, Jan 12, 2011 at 1:12 PM, tom fogal <tfogal at sci.utah.edu> wrote:
> In master/docs/cfg-buildsteps.texinfo we have:
>  @item timeout
>  if the command fails to produce any output for this many seconds, it
>  is assumed to be locked up and will be killed.
>  @item maxTime
>  if the command takes longer than this many seconds, it will be killed.
> These are exactly the same, no?  Are both actually supported?  What
> happens when one sets both; which one "wins"?
> Can we deprecate one && remove it from the documentation?
> -tom

They're slightly different.  Consider the case of the 'yes' command,
which produces 'y' until interrupted.

If you have only timeout set, then this command will never be killed
since it always producing output.

If you set maxTime, then the command will be killed after the
specified number of seconds.

Both are useful for different things.  In general I'd say that
maxTime, if set, should be greater than timeout.


More information about the devel mailing list