From: Noah Misch <noah@leadboat.com>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: On sparc64+ext4, suppress test failures from known WAL read fail
Date: Thu, 27 Jan 2022 02:07:55 +0000
Message-ID: <E1nCuCZ-0005lP-LU@gemulon.postgresql.org> (raw)
On sparc64+ext4, suppress test failures from known WAL read failure.
Buildfarm members kittiwake, tadarida and snapper began to fail
frequently when commits 3cd9c3b921977272e6650a5efbeade4203c4bca2 and
f47ed79cc8a0cfa154dc7f01faaf59822552363f added tests of concurrency, but
the problem was reachable before those commits. Back-patch to v10 (all
supported versions).
Discussion: https://postgr.es/m/20220116210241.GC756210@rfd.leadboat.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/ce6d79368efa8a553490b5b5962bc529d7de54cb
Modified Files
--------------
contrib/amcheck/t/003_cic_2pc.pl | 2 ++
src/test/perl/PostgreSQL/Test/Utils.pm | 23 +++++++++++++++++++++++
src/test/recovery/t/027_stream_regress.pl | 13 ++++++++++++-
3 files changed, 37 insertions(+), 1 deletion(-)
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: noah@leadboat.com
Subject: Re: pgsql: On sparc64+ext4, suppress test failures from known WAL read fail
In-Reply-To: <E1nCuCZ-0005lP-LU@gemulon.postgresql.org>
References: <E1nCuCZ-0005lP-LU@gemulon.postgresql.org>
* 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