pg_upgrade test writes to source directory
Peter Eisentraut <peter.eisentraut@enterprisedb.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2022-05-25T06:21:26Z
Lists: pgsql-hackers
Attachments
- 0001-Run-pg_upgrade-test-in-build-directory.patch (text/plain) patch 0001
The 002_pg_upgrade.pl test leaves a file delete_old_cluster.sh in the
source directory. In vpath builds, there shouldn't be any files written
to the source directory.
Note that the TAP tests run with the source directory as the current
directory, so this is the result of pg_upgrade leaving its output files
in the current directory.
It looks like an addition of
chdir $ENV{TESTOUTDIR};
could fix it. Please check the patch.
Commits
-
Split TESTDIR into TESTLOGDIR and TESTDATADIR
- c47885bd8b69 16.0 landed
-
Don't hardcode tmp_check/ as test directory for tap tests
- bb54bf22900f 16.0 landed
-
Force run of pg_upgrade in the build directory in its TAP test
- 15b6d2155375 15.0 landed
-
Add missing test names in TAP tests of pg_upgrade
- 99f6f19799ed 15.0 landed