Source: liburi-fetch-perl Version: 0.13-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200501 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: 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/00-compile.t ..... > 1..1 > ok 1 - use URI::Fetch; > ok > > # Failed test at t/01-fetch.t line 19. > Can't call method "status" on an undefined value at t/01-fetch.t line 20. > # Looks like your test exited with 2 just after 1. > t/01-fetch.t ....... > 1..80 > not ok 1 > Dubious, test returned 2 (wstat 512, 0x200) > Failed 80/80 subtests > > # Failed test at t/02-freezethaw.t line 17. > Can't call method "http_status" on an undefined value at t/02-freezethaw.t > line 18. > # Looks like your test exited with 2 just after 1. > t/02-freezethaw.t .. > 1..11 > not ok 1 > Dubious, test returned 2 (wstat 512, 0x200) > Failed 11/11 subtests > > Test Summary Report > ------------------- > t/01-fetch.t (Wstat: 512 Tests: 1 Failed: 1) > Failed test: 1 > Non-zero exit status: 2 > Parse errors: Bad plan. You planned 80 tests but ran 1. > t/02-freezethaw.t (Wstat: 512 Tests: 1 Failed: 1) > Failed test: 1 > Non-zero exit status: 2 > Parse errors: Bad plan. You planned 11 tests but ran 1. > Files=3, Tests=3, 1 wallclock secs ( 0.02 usr 0.00 sys + 0.28 cusr 0.04 > csys = 0.34 CPU) > Result: FAIL > Failed 2/3 test programs. 2/3 subtests failed. > make[1]: *** [Makefile:858: test_dynamic] Error 2 > 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/2020/05/01/liburi-fetch-perl_0.13-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.
