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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Banck <mbanck(at)gmx(dot)net>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Maybe BF "timedout" failures are the client script's fault?
Date: 2026-01-12 15:05:47
Message-ID: 3936259.1768230347@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Banck <mbanck(at)gmx(dot)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&br=master

Thanks. At least the reporting is clearer now.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Jones 2026-01-12 15:17:31 Re: [PATCH] psql: add \dcs to list all constraints
Previous Message Tom Lane 2026-01-12 15:01:57 Re: typedef indentation in pg_shmem.h