Re: buildfarm client release 4.18

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: buildfarm-members(at)postgresql(dot)org
Subject: Re: buildfarm client release 4.18
Date: 2016-10-12 00:51:09
Message-ID: 1874.1476233469@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: buildfarm-members pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)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

In response to

Responses

Browse buildfarm-members by date

  From Date Subject
Next Message Andrew Dunstan 2016-10-12 02:34:38 Re: buildfarm client release 4.18
Previous Message Andrew Dunstan 2016-10-12 00:24:34 buildfarm client release 4.18

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2016-10-12 02:32:06 Re: int2vector and btree indexes
Previous Message Andrew Dunstan 2016-10-12 00:24:34 buildfarm client release 4.18