postgres.git / summary / log / commit / refs

commit    da906766cd3bef8290db25bd5c8776c03689f3d5
Author:   Andres Freund <andres@anarazel.de>
Date:     Wed Nov 07 17:22:48 2018 +0000

    Use installcheck-parallel in pg_upgrade's testsuite.
    
    The installcheck run takes a sizable fraction of test.sh to run. Using
    a parallel schedule reduces that noticably.
    
    It's possible that we want to backpatch this at some point, to reduce
    buildfarm times, but for now lets just see if this upsets the
    buildfarm.
    
    Author: Andres Freund
    Discussion: https://postgr.es/m/20181105210039.hh4vvi4vwoq5ba2q@alap3.anarazel.de


 src/bin/pg_upgrade/test.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/bin/pg_upgrade/test.sh b/src/bin/pg_upgrade/test.sh
index f895663dc9f..1d3272dabfa 100644
--- a/src/bin/pg_upgrade/test.sh
+++ b/src/bin/pg_upgrade/test.sh
@@ -169,7 +169,7 @@ createdb "$dbname1" || createdb_status=$?
 createdb "$dbname2" || createdb_status=$?
 createdb "$dbname3" || createdb_status=$?
 
-if "$MAKE" -C "$oldsrc" installcheck; then
+if "$MAKE" -C "$oldsrc" installcheck-parallel; then
 	oldpgversion=`psql -X -A -t -d regression -c "SHOW server_version_num"`
 
 	# before dumping, get rid of objects not existing in later versions


[parent: c6e4133fae1f]