Source: pmtools Version: 2.2.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye
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(1, 'blib/lib', > 'blib/arch')" t/*.t t/lib/*.t > t/basepods.t ..... > 1..3 > ok 1 - basepods runs > ok 2 - found Perl POD > ok 3 - found POD POD > ok > t/faqpods.t ...... > 1..2 > ok 1 - faqpods runs > ok 2 - found a Perl FAQ POD > ok > t/lib/pmtools.t .. > 1..7 > ok 1 - created a pmtools iterator > ok 2 - first POD file, first @INC > ok 3 - middle POD file, first @INC > ok 4 - last POD file, first @INC > ok 5 - last POD file, last @INC > ok 6 - beyond end of filenames > ok 7 - way beyond end of filenames > ok > t/modpods.t ...... > 1..2 > ok 1 - modpods runs > ok 2 - found Tie::Hash > ok > t/pfcat.t ........ > 1..2 > ok 1 - pfcat runs > ok 2 - catted module function > ok > t/plxload.t ...... > 1..1 > ok 1 - modules loaded > ok > t/pmall.t ........ > 1..2 > ok 1 - pmall runs > ok 2 - synopsized all modules > ok > > # Failed test 'found Carp' > # at t/pman.t line 20. > # 'pod2text: unable to format > /usr/lib/x86_64-linux-gnu/perl-base/Carp.pm > # ' > # doesn't match '(?^ms:NAME.*[Cc]arp - \w.*SYNOPSIS.*DESCRIPTION)' > # Looks like you failed 1 test of 2. > t/pman.t ......... > 1..2 > ok 1 - pman runs > not ok 2 - found Carp > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/2 subtests > t/pmcat.t ........ > 1..2 > ok 1 - pmcat runs > ok 2 - catted Carp > ok > t/pmcheck.t ...... > 1..2 > ok 1 - pmcheck runs > ok 2 - pmcheck had output > ok > t/pmdesc.t ....... > 1..2 > ok 1 - pmdesc runs > ok 2 - described a module > ok > t/pmeth.t ........ > 1..2 > ok 1 - pmeth runs > ok 2 - list methods of a module > ok > t/pmexp.t ........ > 1..2 > ok 1 - pmexp runs > ok 2 - listed module exports > ok > t/pmfunc.t ....... > 1..3 > ok 1 - pmfunc runs > ok 2 - found 'chdir()' > ok 3 - display function body > ok > t/pmload.t ....... > 1..2 > ok 1 - pmload runs > ok 2 - listed loaded modules > ok > t/pmls.t ......... > 1..2 > ok 1 - pmls runs > ok 2 - found Tie::Hash > ok > t/pmpath.t ....... > 1..2 > ok 1 - pmpath runs > ok 2 - found Tie::Hash > ok > t/pmvers.t ....... > 1..2 > ok 1 - pmvers runs > ok 2 - found version of Tie::Hash > ok > t/podgrep.t ...... > 1..2 > ok 1 - podgrep runs > ok 2 - found DESCRIPTION > ok > t/pods.t ......... > 1..2 > ok 1 - pods runs > ok 2 - found Tie::Hash > ok > t/podtoc.t ....... > 1..2 > ok 1 - podtoc runs > ok 2 - found Table of Contents > ok > t/sitepods.t ..... > 1..1 > ok 1 - sitepods runs > ok > t/stdpods.t ...... > 1..2 > ok 1 - stdpods runs > ok 2 - found Tie::Hash > ok > > Test Summary Report > ------------------- > t/pman.t (Wstat: 256 Tests: 2 Failed: 1) > Failed test: 2 > Non-zero exit status: 1 > Files=23, Tests=51, 3 wallclock secs ( 0.04 usr 0.03 sys + 2.14 cusr 0.41 > csys = 2.62 CPU) > Result: FAIL > Failed 1/23 test programs. 1/51 subtests failed. > make[2]: *** [Makefile:1077: test_dynamic] Error 255 > make[2]: 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/2020/06/20/pmtools_2.2.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.