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 <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1nnir5-0003Nw-2C
	for pgsql-hackers@arkaria.postgresql.org; Sun, 08 May 2022 15:29:55 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1nniq4-0002qL-Ej
	for pgsql-hackers@arkaria.postgresql.org; Sun, 08 May 2022 15:28:52 +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 <tgl@sss.pgh.pa.us>)
	id 1nniq4-0002qB-5r
	for pgsql-hackers@lists.postgresql.org; Sun, 08 May 2022 15:28:52 +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 <tgl@sss.pgh.pa.us>)
	id 1nnipu-0001oY-Av
	for pgsql-hackers@postgresql.org; Sun, 08 May 2022 15:28:48 +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 248FSYin3254126;
	Sun, 8 May 2022 11:28:34 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: Robert Haas <robertmhaas@gmail.com>, pgsql-hackers@postgresql.org,
        Thomas Munro <thomas.munro@gmail.com>,
        Andrew Dunstan <andrew@dunslane.net>
Subject: Re: failures in t/031_recovery_conflict.pl on CI
In-reply-to: <20220506155827.dfnaheq6ufylwrqf@alap3.anarazel.de>
References: <20220503040557.eimbfibv4rsey3s5@alap3.anarazel.de>
 <1959496.1651555006@sss.pgh.pa.us>
 <20220503182025.wvbebs2ojk6vpi5f@alap3.anarazel.de>
 <2174975.1651602203@sss.pgh.pa.us>
 <20220503191305.htuzje6ldmic7skk@alap3.anarazel.de>
 <2808491.1651802860@sss.pgh.pa.us>
 <20220506030927.6qehktk6bodv4ft3@alap3.anarazel.de>
 <2823814.1651808182@sss.pgh.pa.us>
 <20220506035320.db77mag7nahxzpyy@alap3.anarazel.de>
 <2825879.1651809448@sss.pgh.pa.us>
 <20220506155827.dfnaheq6ufylwrqf@alap3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Fri, 06 May 2022 08:58:27 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3254124.1652023714.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 08 May 2022 11:28:34 -0400
Message-ID: <3254125.1652023714@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: 
 <https://www.postgresql.org/message-id/3254125.1652023714%40sss.pgh.pa.us>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
> On 2022-05-05 23:57:28 -0400, Tom Lane wrote:
>> Are you sure there's just one test that's failing?  I haven't checked
>> the buildfarm history close enough to be sure of that.  But if it's
>> true, disabling just that one would be fine (again, as a stopgap
>> measure).

> I looked through all the failures I found and it's two kinds of failures=
, both
> related to the deadlock test. So I'm thinking of skipping just that test=
 as in
> the attached.

Per lapwing's latest results [1], this wasn't enough.  I'm again thinking
we should pull the whole test from the back branches.

			regards, tom lane

[1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dlapwing&dt=3D=
2022-05-07%2016%3A40%3A04