Re: Release 17 of the PostgreSQL Buildfarm Client - Mailing list buildfarm-members

From Tom Lane
Subject Re: Release 17 of the PostgreSQL Buildfarm Client
Date
Msg-id 3973102.1691198716@sss.pgh.pa.us
Whole thread Raw
In response to Re: Release 17 of the PostgreSQL Buildfarm Client  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Release 17 of the PostgreSQL Buildfarm Client  (Andrew Dunstan <andrew@dunslane.net>)
List buildfarm-members
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



buildfarm-members by date:

Previous
From: Tom Lane
Date:
Subject: Re: Release 17 of the PostgreSQL Buildfarm Client
Next
From: Andrew Dunstan
Date:
Subject: Re: Release 17 of the PostgreSQL Buildfarm Client