Your message dated Mon, 14 Feb 2022 09:48:49 +0000
with message-id <e1njxyt-00082b...@fasolo.debian.org>
and subject line Bug#1005611: fixed in pgbadger 11.7-2
has caused the Debian Bug report #1005611,
regarding pgbadger: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1
returned exit code 2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1005611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pgbadger
Version: 11.7-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> Makefile:899: You must install pod2markdown to generate README.md from
> doc/pgBadger.pod
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness"
> "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib',
> 'blib/arch')" t/*.t
> t/01_lint.t .........
> 1..3
> ok 1 - PERL syntax check
> ok 2 - pod syntax check
> ok 3 - Storable version in this Perl install is buggy, need Perl 5.32 or
> greater
> ok
> t/02_basics.t .......
> 1..17
> ok 1 - Inline help
> ok 2 - Light log report to stdout
> ok 3 - Light log report to HTML
> ok 4 - Light log to binary
> ok 5 - From binary to JSON
> ok 6 - Incremental mode report
> ok 7 - Ressources files in incremental mode
> ok 8 - Light log from STDIN
> ok 9 - Multiple output format '13478015985134780' = '13478015985134780'
> ok 10 - syslog report to stdout
> ok 11 - statement type
> ok 12 - French encoding
> ok 13 - Cyrillic encoding
> ok 14 - Anonymization \#1
> ok 15 - Anonymization \#2
> ok 16 - Anonymization \#3
> ok 17
> ok
> t/03_consistency.t ..
> 1..21
> ok 1 - Generate intermediate binary file from log
> ok 2 - Generate json report from binary file
> ok 3 - Consistent count
> ok 4 - Consistent query_total
> ok 5 - Consistent peak write
> ok 6 - pgBouncer connections
> ok 7 - Generate json report for heroku log file
> ok 8 - Consistent CTE duration
> ok 9 - logplex multiline and new format
> ok 10 - Generate json report from RDS log file with --exclude-client
> ok 11 - Consistent RDS + exclude client
> ok 12 - Generate json report from CloudSQL log file
> ok 13 - Consistent CloudSQL log format
> ok 14 - Generate report from begin time
> ok 15 - Generate report from end time
> ok 16 - Generate report from begin->end time
> ok 17 - Generate report from full log before with end time
> ok 18 - Generate report from single day before with end time
> ok 19 - Generate report from include time
> ok 20 - Generate report from exclude time
> ok 21 - Correct first and last query timestamps on timezone adjusted log
> ok
> grep: /tmp/pgbadger_data_tmp/pgbench/2021/week-07/index.html: No such file or
> directory
>
> # Failed test 'Test incremental mode with --explode and --dbname'
> # at t/04_advanced.t line 32.
> # Looks like you failed 1 test of 9.
> t/04_advanced.t .....
> 1..9
> ok 1 - Test --exclude-db + --explode
> ok 2 - Test --dbname + --explode
> ok 3 - Test incremental mode with --explode
> not ok 4 - Test incremental mode with --explode and --dbname
> ok 5 - Test database exclusion with jsonlog
> ok 6 - Test log_temp_files only
> ok 7 - Test last parse file without incremental mode
> ok 8 - Second pass on last parse file without incremental mode
> ok 9 - Last parse file must not have changed
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/9 subtests
>
> Test Summary Report
> -------------------
> t/04_advanced.t (Wstat: 256 Tests: 9 Failed: 1)
> Failed test: 4
> Non-zero exit status: 1
> Files=4, Tests=50, 110 wallclock secs ( 0.02 usr 0.00 sys + 45.23 cusr 1.07
> csys = 46.32 CPU)
> Result: FAIL
> Failed 1/4 test programs. 1/50 subtests failed.
> make[1]: *** [Makefile:839: test_dynamic] Error 1
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2
The full build log is available from:
http://qa-logs.debian.net/2022/02/12/pgbadger_11.7-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!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: pgbadger
Source-Version: 11.7-2
Done: Christoph Berg <m...@debian.org>
We believe that the bug you reported is fixed in the latest version of
pgbadger, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1005...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christoph Berg <m...@debian.org> (supplier of updated pgbadger package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 14 Feb 2022 10:10:58 +0100
Source: pgbadger
Architecture: source
Version: 11.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers <team+postgre...@tracker.debian.org>
Changed-By: Christoph Berg <m...@debian.org>
Closes: 1005611
Changes:
pgbadger (11.7-2) unstable; urgency=medium
.
* Fix test failure in syslog test. (Closes: #1005611)
Checksums-Sha1:
caa304d95399f9860abc538410b2dc613c452304 2059 pgbadger_11.7-2.dsc
538a26d2f0ba72d250f80e11e8ebba28b43e079b 6196 pgbadger_11.7-2.debian.tar.xz
Checksums-Sha256:
9b67d6e51c5b30024ffa0bc80c3bd11921362a27f61719c0e75eb607a1575396 2059
pgbadger_11.7-2.dsc
40d6d08c2f01d0f5c41901a1883e924087def66923a2f2aa858e02b998ca885a 6196
pgbadger_11.7-2.debian.tar.xz
Files:
ef57d742ea20fbc3a56a547318fd63f8 2059 database optional pgbadger_11.7-2.dsc
fab43dc367137effa55d0ac5c3ac7c6f 6196 database optional
pgbadger_11.7-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmIKIckACgkQTFprqxLS
p651+hAArBeN4NLY+GT1JvpTCQ4L65fKgIvKJ86OCy3pyU8VolAfXBFl340PM9N/
pYGYCn15baqngUDoeTuTIgV9cpAOZJ3cTG3XHghMIiCfcCUxepuqgKXW9AAaVaGh
3RmdOAgj+Dw0/CV3DHL7UbNngwyQ9teX0RmiAf8BhgVGoGVOQUV7dJAhOGJk6FUF
eA1ASqonUF46foavnT7BdxBo8jsLFNGhojiYGYcyrDgJLI0eYfgtyZ2j34ANbIx2
amksTUuuOyOfdySML2HulPJWEDJFLrlLslicAQGLSmci+QWZ2l4ZKVrpxZRfIsJi
hvKd9kCXColJr0V4wmOMfj5bh5k53t1do5zRBRJIacXamNbl9ho+vyz7TnZIy+yk
Qc7wHLIdQ5CJNXE9EAXQOektbTlDlgBLC3MVwZAoOg5vq9B5DKxOpTWv4wHVPKOm
sCElxQyf5Ss8OB6YDZAf3FxPSofLX4wb3LfQOlfdeQF9VcVFHSSWGYo0aRWBC7qQ
5q6CsfMPMz62MZEvbJhGsYCbiV3bJYi6a1/+Eiw+JspJpyUXZuGoc4ZkQ1eBjs/0
Pwh3SbyfkrCqFmbOwk3r63mz3LyG5JCQExsmpb0XHI6rXm8azJJzM53VBNLVaEnC
zRT97Sl4NPC/1wn7q6bkZkOMi778ZZ7VIJ4gUS7KTPQU6iVFyfM=
=dVET
-----END PGP SIGNATURE-----
--- End Message ---
