From: Andres Freund <andres@anarazel.de>
To: Mark Dilger <mark.dilger@enterprisedb.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Melanie Plageman <melanieplageman@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Unstable tests for recovery conflict handling
Date: Wed, 27 Apr 2022 18:26:34 -0700
Message-ID: <20220428012634.xobo2f7ipaeblv6a@alap3.anarazel.de> (raw)
In-Reply-To: <F9294C25-83A0-49F1-9F39-3179739AEF63@enterprisedb.com>
References: <E1nca5h-000nN0-6f@gemulon.postgresql.org>
<394950.1651077914@sss.pgh.pa.us>
<F9294C25-83A0-49F1-9F39-3179739AEF63@enterprisedb.com>
Hi,
On 2022-04-27 10:11:53 -0700, Mark Dilger wrote:
>
>
> > On Apr 27, 2022, at 9:45 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >
> > [ starting a new thread cuz the shared-stats one is way too long ]
> >
> > Andres Freund <andres@anarazel.de> writes:
> >> Add minimal tests for recovery conflict handling.
> >
> > It's been kind of hidden by other buildfarm noise, but
> > 031_recovery_conflict.pl is not as stable as it should be [1][2][3][4].
> >
> > Three of those failures look like
>
> Interesting,
>
> I have been getting failures on REL_14_STABLE:
>
> t/012_subtransactions.pl ............. 11/12
> # Failed test 'Rollback of PGPROC_MAX_CACHED_SUBXIDS+ prepared transaction on promoted standby'
> # at t/012_subtransactions.pl line 211.
> # got: '3'
> # expected: '0'
> t/012_subtransactions.pl ............. 12/12 # Looks like you failed 1 test of 12.
> t/012_subtransactions.pl ............. Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/12 subtests
>
> And the logs, tmp_check/log/regress_log_012_subtransactions, showing:
I'm a bit confused - what's the relation of that failure to this thread / the
tests / this commit?
Greetings,
Andres Freund
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: andres@anarazel.de, mark.dilger@enterprisedb.com, tgl@sss.pgh.pa.us, melanieplageman@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Unstable tests for recovery conflict handling
In-Reply-To: <20220428012634.xobo2f7ipaeblv6a@alap3.anarazel.de>
References: <E1nca5h-000nN0-6f@gemulon.postgresql.org> <394950.1651077914@sss.pgh.pa.us> <F9294C25-83A0-49F1-9F39-3179739AEF63@enterprisedb.com> <20220428012634.xobo2f7ipaeblv6a@alap3.anarazel.de>
* 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