| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, buildfarm-members(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Possible infinite loop on buildfarm animals |
| Date: | 2024-03-17 19:38:46 |
| Message-ID: | 202403171938.34kpjnr7lwb7@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | buildfarm-members |
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?
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"No hay hombre que no aspire a la plenitud, es decir,
la suma de experiencias de que un hombre es capaz"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-03-17 19:43:59 | Re: Possible infinite loop on buildfarm animals |
| Previous Message | Noah Misch | 2024-03-17 17:29:41 | Re: Possible infinite loop on buildfarm animals |