From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
cc: Andres Freund <andres@anarazel.de>, 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: <20220726163339.4mpr5fce7ytbshs5@alvherre.pgsql>
References: <20220726163339.4mpr5fce7ytbshs5@alvherre.pgsql>
Comments: In-reply-to Alvaro Herrera <alvherre@alvh.no-ip.org>
	message dated "Tue, 26 Jul 2022 18:33:39 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2428360.1658854058.1@sss.pgh.pa.us>
Date: Tue, 26 Jul 2022 12:47:38 -0400
Message-ID: <2428361.1658854058@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2428361.1658854058%40sss.pgh.pa.us>
Precedence: bulk

Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Hey, I just noticed that these tests are still disabled.  The next
> minors are coming soon; should we wait until *those* are done and then
> re-enable; or re-enable them now to see how they fare and then
> re-disable before the next minors if there's still problems we don't
> find fixes for?

Maybe I missed it, but I don't think anything's been done to fix the
test's problems in the back branches.

			regards, tom lane