Feedback-ID: ia2694551:Fastmail
Date: Sun, 17 Mar 2024 20:38:46 +0100
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Noah Misch <noah@leadboat.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, buildfarm-members@lists.postgresql.org
Subject: Re: Possible infinite loop on buildfarm animals
Message-ID: <202403171938.34kpjnr7lwb7@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20240317172941.4e@rfd.leadboat.com>
Archived-At: 
 <https://www.postgresql.org/message-id/202403171938.34kpjnr7lwb7%40alvherre.pgsql>
Precedence: bulk

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"