Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nQ9KF-0000mj-4g for pgsql-hackers@arkaria.postgresql.org; Fri, 04 Mar 2022 14:54:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nQ9KE-0007ko-04 for pgsql-hackers@arkaria.postgresql.org; Fri, 04 Mar 2022 14:54:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nQ9KD-0007ke-NB for pgsql-hackers@lists.postgresql.org; Fri, 04 Mar 2022 14:54:33 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nQ9KA-0001MY-Q4 for pgsql-hackers@lists.postgresql.org; Fri, 04 Mar 2022 14:54:33 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 224EsSZd3850537; Fri, 4 Mar 2022 09:54:28 -0500 From: Tom Lane To: Thomas Munro cc: Bharath Rupireddy , PostgreSQL Hackers Subject: Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b In-reply-to: References: Comments: In-reply-to Thomas Munro message dated "Fri, 04 Mar 2022 23:50:46 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3850535.1646405668.1@sss.pgh.pa.us> Date: Fri, 04 Mar 2022 09:54:28 -0500 Message-ID: <3850536.1646405668@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thomas Munro writes: > On Fri, Mar 4, 2022 at 10:37 PM Bharath Rupireddy > 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