From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Noah Misch <noah(at)leadboat(dot)com>, buildfarm-members(at)lists(dot)postgresql(dot)org |
Subject: | Re: Possible infinite loop on buildfarm animals |
Date: | 2024-03-17 19:43:59 |
Message-ID: | 3400216.1710704639@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | buildfarm-members |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> On 2024-Mar-17, Noah Misch wrote:
>> Other than CLOBBER_CACHE animals, the server rejects results older than 24h:
>> https://github.com/PGBuildFarm/server-code/blob/8572ac7/cgi-bin/pgstatus.pl#L273
>> The same 24h should probably be the default wait_timeout. One might use a
>> longer timeout if wanting to attach a debugger to a process of a stuck run.
>> If one just wants an intervention-free buildfarm animal, 24h is good.
> Maybe that should be the default value embedded in the buildfarm client
> script, which can be overridden for specific purposes such as
> CLOBBER_CACHE animals?
We don't normally hard-wire such choices in the script, but it could
be plausible to change build-farm.conf.sample, perhaps like:
# max time in seconds allowed for a single branch run
# undef/0 means unlimited
- wait_timeout => undef,
+ wait_timeout => 24 * 60 * 60,
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2024-04-02 12:42:04 | Server upgrade. |
Previous Message | Alvaro Herrera | 2024-03-17 19:38:46 | Re: Possible infinite loop on buildfarm animals |