Re: Maybe BF "timedout" failures are the client script's fault?

Michael Banck <mbanck@gmx.net> writes:

On Sat, Jan 10, 2026 at 09:34:16AM -0500, Andrew Dunstan wrote:

So in  addition to the above I have added some code to update that
timestamp if the file exists (which should only be the case with a
timeout).

I've applied this to fruitcrow and it now shows correct runtimes for a
timed-out run, see
https://buildfarm.postgresql.org/cgi-bin/show_history.pl?nm=fruitcrow&amp;br=master

Thanks. At least the reporting is clearer now.

regards, tom lane