]> granicus.if.org Git - postgresql/commit
In the pg_upgrade test suite, don't write to src/test/regress.
authorNoah Misch <noah@leadboat.com>
Tue, 28 May 2019 19:59:00 +0000 (12:59 -0700)
committerNoah Misch <noah@leadboat.com>
Tue, 28 May 2019 20:00:16 +0000 (13:00 -0700)
commitc44e9bc3a10f8c6dff07db355375339d7a6db24b
tree2ef3b37233c2782e13bf54f77054ef205a91029e
parent8e2b41ecf8acaf36208fafec4a01ffad04fb69a2
In the pg_upgrade test suite, don't write to src/test/regress.

When this suite runs installcheck, redirect file creations from
src/test/regress to src/bin/pg_upgrade/tmp_check/regress.  This closes a
race condition in "make -j check-world".  If the pg_upgrade suite wrote
to a given src/test/regress/results file in parallel with the regular
src/test/regress invocation writing it, a test failed spuriously.  Even
without parallelism, in "make -k check-world", the suite finishing
second overwrote the other's regression.diffs.  This revealed test
"largeobject" assuming @abs_builddir@ is getcwd(), so fix that, too.

Buildfarm client REL_10, released fifty-four days ago, supports saving
regression.diffs from its new location.  When an older client reports a
pg_upgradeCheck failure, it will no longer include regression.diffs.
Back-patch to 9.5, where pg_upgrade moved to src/bin.

Reviewed (in earlier versions) by Andrew Dunstan.

Discussion: https://postgr.es/m/20181224034411.GA3224776@rfd.leadboat.com
src/bin/pg_upgrade/test.sh
src/test/regress/input/largeobject.source
src/test/regress/output/largeobject.source
src/test/regress/output/largeobject_1.source
src/tools/msvc/vcregress.pl