Horton

Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Michael Paquier <michael@paquier.xyz>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-10-10T14:07:43Z
Lists: pgsql-hackers 
On 03.10.21 09:03, Michael Paquier wrote:
> On Sat, Oct 02, 2021 at 11:34:38PM -0400, Tom Lane wrote:
>> Maybe we could leave test.sh in place for awhile?  I'd rather
>> not cause a flag day for buildfarm owners.  (Also, how do we
>> see this working in the back branches?)
> 
> I would be fine with test.sh staying around for now.

test.sh could be changed to invoke the TAP test.

Commits

  1. Improve and fix some issues in the TAP tests of pg_upgrade

  2. Fix several issues with the TAP tests of pg_upgrade

  3. Make upgradecheck a no-op in MSVC's vcregress.pl

  4. Switch the regression tests of pg_upgrade to use TAP tests

  5. Fix check for PGHOST[ADDR] in pg_upgrade with Windows and temporary paths

  6. Remove REGRESS_OUTPUTDIR environment variable.

  7. Add PostgreSQL::Test::Cluster::config_data()