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.

Reply via email to