From: Tom Lane <tgl@sss.pgh.pa.us>
To: buildfarm-members@lists.postgresql.org
Subject: Possible infinite loop on buildfarm animals
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2530378.1710528134.1@sss.pgh.pa.us>
Date: Fri, 15 Mar 2024 14:42:14 -0400
Message-ID: <2530379.1710528134@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2530379.1710528134%40sss.pgh.pa.us>
Precedence: bulk

Between approximately 11:05 UTC and 13:25 UTC today (15 Mar 2024),
the Postgres git repo contained a buggy test recipe that caused
an infinite loop that will eventually exhaust disk space.
If you have any animals that might have launched a test run on
HEAD in that interval, you might want to check up on them.
A manual kill of the process that's consuming 100% CPU should
be enough to get out of it.

Another idea to consider is to set the wait_timeout parameter
in your animals' configuration files, to put an upper bound
on the total elapsed time for a run.  By default that's
infinite, since it's really hard to select a one-size-fits-all
value ... but it's a good backstop if you don't mind picking
machine-specific limits.

			regards, tom lane