| 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-05 01:25:16 |
| Message-ID: | 3973102.1691198716@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | buildfarm-members pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2023-08-05 10:40:27 | Re: Release 17 of the PostgreSQL Buildfarm Client |
| Previous Message | Tom Lane | 2023-08-04 23:14:25 | Re: Release 17 of the PostgreSQL Buildfarm Client |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2023-08-05 01:39:24 | Re: Is RecoveryConflictInterrupt() entirely safe in a signal handler? |
| Previous Message | Peter Geoghegan | 2023-08-05 00:53:39 | Re: Use of additional index columns in rows filtering |