Re: pg_upgrade test failure - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: pg_upgrade test failure
Date
Msg-id YykWlaJj3dphGBvR@paquier.xyz
Whole thread Raw
In response to Re: pg_upgrade test failure  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Mon, Sep 19, 2022 at 06:13:17PM -0700, Andres Freund wrote:
> I don't really see what'd race with what here? pg_upgrade has precise control
> over what's happening here, no?

A code path could have forgotten a fclose() for example, but this code
is rather old and close-proof as far as I know.  Most of the log files
are used with redirections for external calls, though  I don't see
how these could still be hold after pg_upgrade finishes, though :/
Could the use meson somewhat influence when running tests on Windows?

> I've only seen it once so far, but there haven't been many CI runs of the
> meson branch since rebasing ontop of the last changes to pg_upgrade.

Hmm, okay.  Is that a specific branch in one of your public repos?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Reducing the chunk header sizes on all memory context types
Next
From: Justin Pryzby
Date:
Subject: Re: pg_upgrade test failure