Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b
Date
Msg-id CA+hUKG+54=sy=7pCJRb2Y_fiR1tSFE5_zx8PyfJONY7BCZuRmg@mail.gmail.com
Whole thread Raw
In response to Regression tests failures on Windows Server 2019 - on master at commit # d816f366b  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Mar 4, 2022 at 10:37 PM Bharath Rupireddy
<bharath.rupireddyforpostgres@gmail.com> wrote:
> It looks like regression tests are failing on Windows Server 2019 [1].
> Ignore if it's reported elsewhere.

It's broken since 46ab07ff "Clean up assorted failures under clang's
-fsanitize=undefined checks.":

https://github.com/postgres/postgres/commits/master

I don't see what that patch has to do with the symptoms.  It looks a
bit like the cluster started by the "startcreate" step ("pg_ctl.exe
start ...") is mysteriously no longer running when we get to the
"test_pl" step ("Connection refused").



pgsql-hackers by date:

Previous
From: Andrey Lepikhov
Date:
Subject: Re: Removing unneeded self joins
Next
From: Justin Pryzby
Date:
Subject: Re: [Proposal] vacuumdb --schema only