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

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

Hi

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).
>
> See https://github.com/PGBuildFarm/client-code/commit/e5d67a35a0136a53e441fccf0ecc9b1b6322526c

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
and
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fruitcrow&dt=2026-01-12%2008%3A10%3A04

Thanks!

Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Roman Khapov 2026-01-12 09:36:22 Re: amcheck: support for GiST
Previous Message John Naylor 2026-01-12 09:27:00 Re: vectorized CRC on ARM64