From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | buildfarm-members(at)postgresql(dot)org |
Subject: | Re: buildfarm client release 4.18 |
Date: | 2016-10-12 02:34:38 |
Message-ID: | 8e0683e1-0365-fa1d-97f6-e93e7eb37b29@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | buildfarm-members pgsql-hackers |
On 10/11/2016 08:51 PM, Tom Lane wrote:
> 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.
>
>
Yeah, unfortunately. I can look at making it report something, not sure
exactly how much will be possible.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2016-10-16 21:22:12 | PG buildfarm member macaque |
Previous Message | Tom Lane | 2016-10-12 00:51:09 | Re: buildfarm client release 4.18 |
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2016-10-12 03:19:44 | Re: DISTINCT with btree skip scan |
Previous Message | Amit Langote | 2016-10-12 02:32:06 | Re: int2vector and btree indexes |