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: <3951994.1691190865@sss.pgh.pa.us>
References: <6e00da65-f0dc-3fa7-8b06-49385e08d05c@dunslane.net>
 <3951994.1691190865@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Fri, 04 Aug 2023 19:14:25 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3973101.1691198716.1@sss.pgh.pa.us>
Date: Fri, 04 Aug 2023 21:25:16 -0400
Message-ID: <3973102.1691198716@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3973102.1691198716%40sss.pgh.pa.us>
Precedence: bulk

I wrote:
> 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.

Further testing shows that a pre-existing force-one-run file does
get removed, so use-cases involving manual creation of the file
are still OK.  Maybe this "force twice" from --force has been
there all along, and nobody noticed?  Even if it's a new bug,
it's not a show-stopper.

			regards, tom lane