[Pkg-postgresql-public] Bug#897523: check-postgres: FTBFS: tests failed

Wed May 2 21:43:12 BST 2018

Source: check-postgres
Version: 2.23.0-1
Severity: serious
Tags: buster sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<<PKGBUILDDIR>>'
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
> t/00_basic.t ............... ok
> t/00_release.t ............. skipped: Test skipped unless environment variable RELEASE_TESTING is set
> t/00_signature.t ........... skipped: Test skipped unless environment variable RELEASE_TESTING is set
> t/00_test_tester.t ......... skipped: Test skipped unless environment variable RELEASE_TESTING is set
> t/01_validate_range.t ...... ok
> # Creating database in directory "test_database_check_postgres"
> Creating new symlink socket at /tmp/cptesting_socket
> t/02_autovac_freeze.t ...... ok
> t/02_backends.t ............ ok
> t/02_bloat.t ............... ok
> t/02_checkpoint.t .......... ok
> t/02_cluster_id.t .......... ok
> t/02_commitratio.t ......... ok
> t/02_connection.t .......... ok
> t/02_custom_query.t ........ ok
> t/02_database_size.t ....... ok
> t/02_dbstats.t ............. ok
> t/02_disabled_triggers.t ... ok
> t/02_disk_space.t .......... ok
> t/02_fsm_pages.t ........... ok
> t/02_fsm_relations.t ....... ok
> t/02_hitratio.t ............ ok
> t/02_last_analyze.t ........ ok
> t/02_last_vacuum.t ......... ok
> t/02_listener.t ............ ok
> t/02_locks.t ............... ok
> t/02_logfile.t ............. ok
> t/02_new_version_bc.t ...... skipped: Skipped because environment variable SKIP_NETWORK_TESTS is set
> t/02_new_version_box.t ..... skipped: Skipped because environment variable SKIP_NETWORK_TESTS is set
> t/02_new_version_cp.t ...... skipped: Skipped because environment variable SKIP_NETWORK_TESTS is set
> t/02_new_version_pg.t ...... skipped: Skipped because environment variable SKIP_NETWORK_TESTS is set
> t/02_new_version_tnm.t ..... skipped: Skipped because environment variable SKIP_NETWORK_TESTS is set
> NOTICE:  schema "pgagent" does not exist, skipping
> NOTICE:  drop cascades to 4 other objects
> DETAIL:  drop cascades to table pgagent.pga_job
> drop cascades to table pgagent.pga_jobstep
> drop cascades to table pgagent.pga_joblog
> drop cascades to table pgagent.pga_jobsteplog
> t/02_pgagent_jobs.t ........ ok
> t/02_pgbouncer_checksum.t .. ok
> t/02_prepared_txns.t ....... ok
> t/02_query_runtime.t ....... ok
> t/02_query_time.t .......... ok
> t/02_relation_size.t ....... ok
> t/02_replicate_row.t ....... ok
> # Connected as 5432:/tmp/cptesting_socket:postgres
> t/02_replication_slots.t ... ok
> # Creating database in directory "test_database_check_postgres2"
> Creating new symlink socket at /tmp/cptesting_socket2
> # Creating database in directory "test_database_check_postgres3"
> Creating new symlink socket at /tmp/cptesting_socket3
> NOTICE:  language "plperlu" does not exist, skipping
> 
> #   Failed test 'Action 'same_schema' reports index 'unique' differences'
> #   at t/02_same_schema.t line 621.
> #                   'POSTGRES_SAME_SCHEMA CRITICAL: DB "postgres" (hosts:/tmp/cptesting_socket,/tmp/cptesting_socket2) Databases were different. Items not matched: 1 | time=0.28s 
> # DB 1: dbservice= port=5432 host=/tmp/cptesting_socket dbname=postgres user=check_postgres_testing 
> # DB 1: PG version: 10.3
> # DB 1: Total objects: 21
> # DB 2: dbservice= port=5432 host=/tmp/cptesting_socket2 dbname=postgres user=check_postgres_testing 
> # DB 2: PG version: 10.3
> # DB 2: Total objects: 21
> # Index "public.valen":
> #  "indexdef" is different:
> #     Database 1: CREATE INDEX valen ON public.gkar USING btree (garibaldi)
> #     Database 2: CREATE UNIQUE INDEX valen ON public.gkar USING btree (garibaldi)
> #  "indisunique" is different:
> #     Database 1: f
> #     Database 2: t
> #  
> # '
> #     doesn't match '(?^s:^POSTGRES_SAME_SCHEMA CRITICAL.*Items not matched: 1 .*
> # \s*Index "public.valen":
> # \s*"indexdef" is different:
> # \s*Database 1: CREATE INDEX valen ON gkar USING btree \(garibaldi\)
> # \s*Database 2: CREATE UNIQUE INDEX valen ON gkar USING btree \(garibaldi\)
> # \s*"indisunique" is different:
> # \s*Database 1: f
> # \s*Database 2: t\s*$)'
> # Looks like you failed 1 test of 76.
> t/02_same_schema.t ......... 
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/76 subtests 
> t/02_sequence.t ............ ok
> t/02_settings_checksum.t ... ok
> t/02_slony_status.t ........ ok
> t/02_timesync.t ............ ok
> # Connected as 5432:/tmp/cptesting_socket:postgres
> t/02_txn_idle.t ............ ok
> t/02_txn_time.t ............ ok
> t/02_txn_wraparound.t ...... ok
> t/02_version.t ............. ok
> t/02_wal_files.t ........... ok
> t/03_translations.t ........ skipped: Test skipped unless environment variable RELEASE_TESTING is set
> t/04_timeout.t ............. ok
> t/05_docs.t ................ ok
> t/99_cleanup.t ............. ok
> t/99_perlcritic.t .......... skipped: Test skipped unless environment variable RELEASE_TESTING is set
> t/99_pod.t ................. skipped: Test skipped unless environment variable RELEASE_TESTING is set
> t/99_spellcheck.t .......... skipped: Test skipped unless environment variable RELEASE_TESTING is set
> 
> Test Summary Report
> -------------------
> t/02_same_schema.t       (Wstat: 256 Tests: 76 Failed: 1)
>   Failed test:  64
>   Non-zero exit status: 1
> Files=55, Tests=916, 138 wallclock secs ( 0.22 usr  0.04 sys + 67.54 cusr 12.82 csys = 80.62 CPU)
> Result: FAIL
> Failed 1/55 test programs. 1/916 subtests failed.
> make[2]: *** [Makefile:794: test_dynamic] Error 255

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/check-postgres_2.23.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.