Subject: Re: buildfarm client release 4.18
To: Tom Lane <tgl@sss.pgh.pa.us>
References: <d42f4f4f-8f0e-6e9d-0af2-e13d4ca1cc74@dunslane.net>
 <1874.1476233469@sss.pgh.pa.us>
Cc: buildfarm-members@postgresql.org
From: Andrew Dunstan <andrew@dunslane.net>
Message-ID: <8e0683e1-0365-fa1d-97f6-e93e7eb37b29@dunslane.net>
Date: Tue, 11 Oct 2016 22:34:38 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <1874.1476233469@sss.pgh.pa.us>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: buildfarm-members-owner@postgresql.org


On 10/11/2016 08:51 PM, Tom Lane wrote:
> 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.
>
> 			


Yeah, unfortunately. I can look at making it report something, not sure 
exactly how much will be possible.

cheers

andrew


-- 
Sent via buildfarm-members mailing list (buildfarm-members@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/buildfarm-members