pgsql: Fix portability issue in pg_upgrade test script: avoid $PWD. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Fix portability issue in pg_upgrade test script: avoid $PWD.
Date
Msg-id E1ZCW3r-0003PC-CO@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix portability issue in pg_upgrade test script: avoid $PWD.

SUSv2-era shells don't set the PWD variable, though anything more modern
does.  In the buildfarm environment this could lead to test.sh executing
with PWD pointing to $HOME or another high-level directory, so that there
were conflicts between concurrent executions of the test in different
branch subdirectories.  This appears to be the explanation for recent
intermittent failures on buildfarm members binturong and dingo (and might
well have something to do with the buildfarm script's failure to capture
log files from pg_upgrade tests, too).

To fix, just use `pwd` in place of $PWD.  AFAICS test.sh is the only place
in our source tree that depended on $PWD.  Back-patch to all versions
containing this script.

Per buildfarm.  Thanks to Oskari Saarenmaa for diagnosing the problem.

Branch
------
REL9_3_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/dca992d8b099ab71b14cd4aa09f31506e3903224

Modified Files
--------------
contrib/pg_upgrade/test.sh |    5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Fix portability issue in pg_upgrade test script: avoid $PWD.
Next
From: Fujii Masao
Date:
Subject: pgsql: Fix incorrect path in pg_regress log messages.