Re: PXGS vs TAP tests
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Noah Misch <noah@leadboat.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-06-20T14:45:21Z
Lists: pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes: > The recipe for running TAP tests in src/Makefile.global doesn't work for > the PGXS case. If you try it you get something like this: > ... > Notice those bogus settings for top_builddir, PG_REGRESS and > REGRESS_SHLIB. The attached patch fixes this bug. OK, but does the 'prove_check' macro need similar adjustments? > I removed the REGRESS_SHLIB setting altogether for the PGXS case - it's > not clear to me why we need it in a TAP test recipe at all. After some digging in the git history, it looks like it's there because of Noah's c09850992, which makes me wonder whether 017_shm.pl requires it. If so, it'd make more sense perhaps for that one test script to set up the environment variable than to have it cluttering every TAP run. (In any case, please don't push this till after beta2 is tagged. We don't need possible test instability right now.) regards, tom lane
Commits
-
Fix prove_installcheck to use correct paths when used with PGXS
- a0fc81326646 15.0 landed
- d173a4699220 9.6.23 landed
- 16ed3ddbbbda 10.18 landed
- 58ac8300bdd4 11.13 landed
- a40f8ea0f555 12.8 landed
- a8b564b0c9c3 13.4 landed
- c4774ce339be 14.0 landed