Re: pg_upgrade test writes to source directory
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
Michael Paquier <michael@paquier.xyz>,
Justin Pryzby <pryzby@telsasoft.com>, pgsql-hackers@postgresql.org
Date: 2022-08-11T15:26:39Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes: > On 2022-06-01 10:55:28 -0400, Tom Lane wrote: >> [...] I'm definitely not happy with the proposed changes to >> 010_tab_completion.pl. My recollection is that those tests >> were intentionally written to test tab completion involving a >> directory name, but this change just loses that aspect entirely. > How about creating a dedicated directory for the created files, to maintain > that? My goal of being able to redirect the test output elsewhere can be > achieved with just a hunk like this: Sure, there's no need for these files to be in the exact same place that the output is collected. I just want to keep their same relationship to the test's CWD. > Of course it'd need a comment adjustment etc. It's a bit ugly to use a > otherwise empty tmp_check/ directory just to reduce the diff size, but it's > also not too bad. Given that it's no longer going to be the same tmp_check dir used elsewhere, maybe we could s/tmp_check/tab_comp_dir/g or something like that? That'd add some clarity I think. regards, tom lane
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