From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
cc: "buildfarm-members@lists.postgresql.org"
 <buildfarm-members@lists.postgresql.org>
Subject: Re: Release 17 of the PostgreSQL Buildfarm Client
In-reply-to: <6e00da65-f0dc-3fa7-8b06-49385e08d05c@dunslane.net>
References: <6e00da65-f0dc-3fa7-8b06-49385e08d05c@dunslane.net>
Comments: In-reply-to Andrew Dunstan <andrew@dunslane.net>
	message dated "Fri, 04 Aug 2023 11:23:11 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3951993.1691190865.1@sss.pgh.pa.us>
Date: Fri, 04 Aug 2023 19:14:25 -0400
Message-ID: <3951994.1691190865@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3951994.1691190865%40sss.pgh.pa.us>
Precedence: bulk

Andrew Dunstan <andrew@dunslane.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