Re: pg_upgrade test writes to source directory
Peter Eisentraut <peter.eisentraut@enterprisedb.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Justin Pryzby <pryzby@telsasoft.com>,
Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers@postgresql.org
Date: 2022-05-27T12:45:57Z
Lists: pgsql-hackers
On 26.05.22 22:52, Justin Pryzby wrote:
> On Fri, May 27, 2022 at 05:43:04AM +0900, Michael Paquier wrote:
>> On Thu, May 26, 2022 at 04:36:47PM +0200, Peter Eisentraut wrote:
>>> I chose TESTOUTDIR because it corresponds to the tmp_check directory, so
>>> that the output files of the pg_upgrade run are removed when the test
>>> artifacts are cleaned up. When using TESTDIR, the pg_upgrade output files
>>> end up in the build directory, which is less bad than the source directory,
>>> but still not ideal.
>>
>> Where does the choice of TESTOUTDIR come from? I am a bit surprised
>> by this choice, to be honest, because there is no trace of it in the
>> buildfarm client or the core code. TESTDIR, on the other hand, points
>> to tmp_check/ if not set. It gets set it in vcregress.pl and
>> Makefile.global.in.
>
> It looks like Peter working on top of the meson branch.
> TESTOUTDIR is not yet in master.
Ooops, yeah. :)
I think you can just chdir to ${PostgreSQL::Test::Utils::tmp_check}.
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