Regression tests unstable
df7cb opened this issue · comments
Christoph Berg commented
Seen a few times on s390x while building the Debian packages:
21:27:52 ### PostgreSQL 11 installcheck ###
21:27:52 Creating new PostgreSQL cluster 11/regress ...
21:27:55 /usr/lib/postgresql/11/lib/pgxs/src/makefiles/../../src/test/regress/pg_regress --inputdir=./ --bindir='/usr/lib/postgresql/11/bin' --dbname=contrib_regression squeeze
21:27:55 (using postmaster on localhost, port 5432)
21:27:55 ============== dropping database "contrib_regression" ==============
21:27:55 NOTICE: database "contrib_regression" does not exist, skipping
21:27:55 DROP DATABASE
21:27:55 ============== creating database "contrib_regression" ==============
21:27:55 CREATE DATABASE
21:27:55 ALTER DATABASE
21:27:55 ============== running regression test queries ==============
21:27:55 test squeeze ... FAILED
21:27:55
21:27:55 ======================
21:27:55 1 of 1 tests failed.
21:27:55 ======================
21:27:55
21:27:55 The differences that caused some tests to fail can be viewed in the
21:27:55 file "/tmp/autopkgtest.WpStPf/tree/regression.diffs". A copy of the test summary that you see
21:27:55 above is saved in the file "/tmp/autopkgtest.WpStPf/tree/regression.out".
21:27:55
21:27:55 make: *** [/usr/lib/postgresql/11/lib/pgxs/src/makefiles/pgxs.mk:403: installcheck] Error 1
21:27:55 *** /tmp/pg_virtualenv.UtmBYH/log/postgresql-11-regress.log (last 100 lines) ***
21:27:55 2023-09-17 19:27:53.203 UTC [2842] LOG: listening on IPv4 address "127.0.0.1", port 5432
21:27:55 2023-09-17 19:27:53.203 UTC [2842] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
21:27:55 2023-09-17 19:27:53.210 UTC [2843] LOG: database system was shut down at 2023-09-17 19:27:53 UTC
21:27:55 2023-09-17 19:27:53.212 UTC [2842] LOG: database system is ready to accept connections
21:27:55 2023-09-17 19:27:53.797 UTC [2850] [unknown]@[unknown] LOG: incomplete startup packet
21:27:55 2023-09-17 19:27:55.541 UTC [2889] WARNING: 1 squeeze worker(s) already running on database oid=16384
21:27:55 2023-09-17 19:27:55.543 UTC [2886] postgres@contrib_regression ERROR: could not start background process
21:27:55 2023-09-17 19:27:55.543 UTC [2886] postgres@contrib_regression HINT: More details may be available in the server log.
21:27:55 2023-09-17 19:27:55.543 UTC [2886] postgres@contrib_regression STATEMENT: SELECT squeeze.squeeze_table('public', 'a', NULL);
21:27:55 2023-09-17 19:27:55.557 UTC [2888] LOG: logical decoding found consistent point at 0/16F4B60
21:27:55 2023-09-17 19:27:55.557 UTC [2888] DETAIL: There are no running transactions.
21:27:55 2023-09-17 19:27:55.559 UTC [2888] LOG: logical decoding found consistent point at 0/16FC698
21:27:55 2023-09-17 19:27:55.559 UTC [2888] DETAIL: There are no running transactions.
21:27:55 2023-09-17 19:27:55.561 UTC [2888] LOG: logical decoding found consistent point at 0/1715728
21:27:55 2023-09-17 19:27:55.561 UTC [2888] DETAIL: There are no running transactions.
21:27:55 Dropping cluster 11/regress ...
21:27:55 **** regression.diffs ****
21:27:55 --- /tmp/autopkgtest.WpStPf/tree/expected/squeeze.out 2023-09-11 14:14:48.000000000 +0000
21:27:55 +++ /tmp/autopkgtest.WpStPf/tree/results/squeeze.out 2023-09-17 19:27:55.552551816 +0000
21:27:55 @@ -11,11 +11,8 @@
21:27:55 FROM generate_series(1, 10) AS g(x);
21:27:55 -- The trivial case.
21:27:55 SELECT squeeze.squeeze_table('public', 'a', NULL);
21:27:55 - squeeze_table
21:27:55 ----------------
21:27:55 -
21:27:55 -(1 row)
21:27:55 -
21:27:55 +ERROR: could not start background process
21:27:55 +HINT: More details may be available in the server log.
21:27:55 SELECT * FROM a;
21:27:55 i | j
21:27:55 ----+----
21:27:55
Christoph Berg commented
The build just now worked, let's hope that was it. Thanks!