pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-hackers@postgresql.org, Thomas Munro <thomas.munro@gmail.com>
Subject: Re: failures in t/031_recovery_conflict.pl on CI
Date: Thu, 05 May 2022 22:07:40 -0400
Message-ID: <2808491.1651802860@sss.pgh.pa.us> (raw)
In-Reply-To: <20220503191305.htuzje6ldmic7skk@alap3.anarazel.de>
References: <907760.1649790322@sss.pgh.pa.us>
	<20220413002626.udl7lll7f3o7nre7@alap3.anarazel.de>
	<20220429200809.uuuseakmhb57sppk@alap3.anarazel.de>
	<465685.1651274819@sss.pgh.pa.us>
	<20220503014803.uknu3cwahwhbgrak@alap3.anarazel.de>
	<1929823.1651549472@sss.pgh.pa.us>
	<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>

Andres Freund <andres@anarazel.de> writes:
> Attached is a fix for the test that I think should avoid the problem. Couldn't
> repro it with it applied, under both rr and valgrind.

May I ask where we're at on this?  Next week's back-branch release is
getting uncomfortably close, and I'm still seeing various buildfarm
animals erratically failing on 031_recovery_conflict.pl.  Should we
just remove that test from the back branches for now?

Also, it appears that the back-patch of pump_until failed to remove
some pre-existing copies, eg check-world in v14 now reports

Subroutine pump_until redefined at t/013_crash_restart.pl line 248.
Subroutine pump_until redefined at t/022_crash_temp_files.pl line 272.

I didn't check whether these are exact duplicates.

			regards, tom lane





view thread (38+ messages)  latest in thread

Message-ID: <2808491.1651802860@sss.pgh.pa.us>
Permalink:  ../2808491.1651802860@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2808491.1651802860@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, robertmhaas@gmail.com, thomas.munro@gmail.com
  Subject: Re: failures in t/031_recovery_conflict.pl on CI
  In-Reply-To: <2808491.1651802860@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox