public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Andrew Dunstan <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: Release 17 of the PostgreSQL Buildfarm Client
Date: Fri, 04 Aug 2023 21:25:16 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

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

view thread (5+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Release 17 of the PostgreSQL Buildfarm Client
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox