| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Subject: | Re: failures in t/031_recovery_conflict.pl on CI |
| Date: | 2022-05-06 02:07:40 |
| Message-ID: | 2808491.1651802860@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2022-05-06 02:08:31 | Re: [EXTERNAL] Re: pg_stat_statements |
| Previous Message | Masahiko Sawada | 2022-05-06 01:53:47 | Re: Logical replication timeout problem |