Source: pmtools Version: 1.54-1 Severity: serious Tags: jessie sid User: [email protected] Usertags: qa-ftbfs-20140114 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" "-e" > "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t > t/basepods.t .. ok > t/faqpods.t ... ok > t/modpods.t ... ok > t/pfcat.t ..... ok > t/plxload.t ... ok > t/pmall.t ..... ok > t/pman.t ...... ok > t/pmcat.t ..... ok > t/pmcheck.t ... ok > > # Failed test 'described a module' > # at t/pmdesc.t line 19. > # 'English (1.06_01) - use nice English (or awk) names for > ugly punctuation variables > # ' > # doesn't match '(?^:English \(\d+\.\d+\) - \w)' > # Looks like you failed 1 test of 2. > t/pmdesc.t .... > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/2 subtests > t/pmeth.t ..... ok > t/pmexp.t ..... ok > t/pmfunc.t .... ok > t/pmload.t .... ok > t/pmls.t ...... ok > t/pmpath.t .... ok > t/pmvers.t .... ok > t/podgrep.t ... ok > t/pods.t ...... ok > t/podtoc.t .... ok > t/sitepods.t .. ok > t/stdpods.t ... ok > > Test Summary Report > ------------------- > t/pmdesc.t (Wstat: 256 Tests: 2 Failed: 1) > Failed test: 2 > Non-zero exit status: 1 > Files=22, Tests=42, 6 wallclock secs ( 0.11 usr 0.11 sys + 4.40 cusr 1.53 > csys = 6.15 CPU) > Result: FAIL > Failed 1/22 test programs. 1/42 subtests failed. > make[2]: *** [test_dynamic] Error 255 > make[2]: Leaving directory `/«PKGBUILDDIR»' > dh_auto_test: make -j1 test returned exit code 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/01/14/pmtools_1.54-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. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
