From: Andrew Dunstan <andrew@dunslane.net>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix pgperlsyncheck following SSL TAP test refactoring
Date: Sun, 10 Apr 2022 13:19:45 +0000
Message-ID: <E1ndXTk-001Bah-Mn@gemulon.postgresql.org> (raw)
Fix pgperlsyncheck following SSL TAP test refactoring
Commit 4a7e964fc6 made pgperlsyncheck fail, but apparently nobody
noticed, although the buildfarm module that does more or less the same
thing was modified. So fix the in-core test. I will look at unifying the
two sets of tests so we avoid a future mismatch.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/c835dcdab622813bb1ccd130458065089f2ccacd
Modified Files
--------------
src/tools/perlcheck/pgperlsyncheck | 2 +-
1 file changed, 1 insertion(+), 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: andrew@dunslane.net
Subject: Re: pgsql: Fix pgperlsyncheck following SSL TAP test refactoring
In-Reply-To: <E1ndXTk-001Bah-Mn@gemulon.postgresql.org>
References: <E1ndXTk-001Bah-Mn@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