Re: Release 17 of the PostgreSQL Buildfarm Client

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: "buildfarm-members(at)lists(dot)postgresql(dot)org" <buildfarm-members(at)lists(dot)postgresql(dot)org>
Subject: Re: Release 17 of the PostgreSQL Buildfarm Client
Date: 2023-08-04 23:14:25
Message-ID: 3951994.1691190865@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: buildfarm-members pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> I have pushed Release 17 of the PostgreSQL Buildfarm client.

I ran a test of this using

run_branches.pl --run-all --nosend --force

and noticed that it created "animal.force-one-run" files in each
of the per-branch directories, and never removed them. This
means (I assume) that the next run will also behave like --force
... and maybe all later ones too, until I manually remove those
files?

I'm not sure if this behavior is new in v17, or I just never
tried it before. I usually create force-one-run files manually.

regards, tom lane

In response to

Responses

Browse buildfarm-members by date

  From Date Subject
Next Message Tom Lane 2023-08-05 01:25:16 Re: Release 17 of the PostgreSQL Buildfarm Client
Previous Message Andrew Dunstan 2023-08-04 15:23:11 Release 17 of the PostgreSQL Buildfarm Client

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2023-08-04 23:34:04 Re: Use of additional index columns in rows filtering
Previous Message Chapman Flack 2023-08-04 20:50:17 Re: Extract numeric filed in JSONB more effectively