Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b
Date: 2022-03-04 14:54:28
Message-ID: 3850536.1646405668@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> On Fri, Mar 4, 2022 at 10:37 PM Bharath Rupireddy
> <bharath(dot)rupireddyforpostgres(at)gmail(dot)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.

The buildfarm is not unhappy, so I'd be looking at what changed
recently in the cfbot's setup.

I find it a little suspicious that startcreate is merrily starting
the postmaster on port 5432, without concern for the possibility
that that port is in use or blocked by a packet filter.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2022-03-04 16:10:39 Re: Add LZ4 compression in pg_dump
Previous Message Matthias van de Meent 2022-03-04 14:37:32 Re: New Table Access Methods for Multi and Single Inserts