There was some recent discussion about making "make check-world" faster.
I'm all for that, but how about making it quieter?  On both machines I've
run it on (CentOS6.8 and Ubuntu 16.04.2), it dumps some gibberish to
stderr, example attached.  Which first made me wonder whether the test
passed or failed, and then made me give up on running it altogether when I
couldn't easily figure that out. Am I supposed to be seeing this?  Am I
supposed to understand it?

Also, it runs in about 8 minutes, not the 20 minutes reported by others.
My system is virtualized, and not particularly fast.  I wonder if it is
failing early somewhere without running to completion? How would/should I
know?

Cheers,

Jeff
+ standard_initdb 
/home/jjanes/pgsql/git/src/bin/pg_upgrade/tmp_check/install//usr/local/pgsql/bin/initdb
+ 
/home/jjanes/pgsql/git/src/bin/pg_upgrade/tmp_check/install//usr/local/pgsql/bin/initdb
 -N

WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
+ [ -n  -a -r  ]
+ ../../test/regress/pg_regress --config-auth 
/home/jjanes/pgsql/git/src/bin/pg_upgrade/tmp_check/data.old
+ 
/home/jjanes/pgsql/git/src/bin/pg_upgrade/tmp_check/install//usr/local/pgsql/bin/pg_ctl
 start -l /home/jjanes/pgsql/git/src/bin/pg_upgrade/log/postmaster1.log -o -F 
-c listen_addresses= -k "/tmp/pg_upgrade_check-rP2T4V" -w
+ awk BEGIN { for (i= 1; i < 46; i++)
        if (i != 7 && i != 10 && i != 13) printf "%c", i }
+ dbname1=        !"#$%&'()*+,-
+ dbname1=\"\     !"#$%&'()*+,-\\"\\\
+ awk BEGIN { for (i = 46; i <  91; i++) printf "%c", i }
+ dbname2=./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ
+ awk BEGIN { for (i = 91; i < 128; i++) printf "%c", i }
+ dbname3=[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
+ createdb \"\    !"#$%&'()*+,-\\"\\\
+ createdb ./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ
+ createdb [\]^_`abcdefghijklmnopqrstuvwxyz{|}~
+ make -C /home/jjanes/pgsql/git installcheck
NOTICE:  database "regression" does not exist, skipping
+ pg_dumpall -f /home/jjanes/pgsql/git/src/bin/pg_upgrade/tmp_check/dump1.sql
+ [ /home/jjanes/pgsql/git != /home/jjanes/pgsql/git ]
+ 
/home/jjanes/pgsql/git/src/bin/pg_upgrade/tmp_check/install//usr/local/pgsql/bin/pg_ctl
 -m fast stop
+ [ -n  ]
+ [ -n  ]
+ [ -n  ]
+ [ -n  ]
+ PGDATA=/home/jjanes/pgsql/git/src/bin/pg_upgrade/tmp_check/data
+ standard_initdb initdb
+ initdb -N

WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
+ [ -n  -a -r  ]
+ ../../test/regress/pg_regress --config-auth 
/home/jjanes/pgsql/git/src/bin/pg_upgrade/tmp_check/data
+ pg_upgrade -d /home/jjanes/pgsql/git/src/bin/pg_upgrade/tmp_check/data.old -D 
/home/jjanes/pgsql/git/src/bin/pg_upgrade/tmp_check/data -b 
/home/jjanes/pgsql/git/src/bin/pg_upgrade/tmp_check/install//usr/local/pgsql/bin
 -B 
/home/jjanes/pgsql/git/src/bin/pg_upgrade/tmp_check/install//usr/local/pgsql/bin
 -p 50848 -P 50848
+ pg_ctl start -l /home/jjanes/pgsql/git/src/bin/pg_upgrade/log/postmaster2.log 
-o -F -c listen_addresses= -k "/tmp/pg_upgrade_check-rP2T4V" -w
+ sh ./analyze_new_cluster.sh
+ pg_dumpall -f /home/jjanes/pgsql/git/src/bin/pg_upgrade/tmp_check/dump2.sql
+ pg_ctl -m fast stop
+ set +x
-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Reply via email to