Source: mail-spf-perl Version: 2.9.0-2 Severity: serious Tags: jessie sid User: [email protected] Usertags: qa-ftbfs-20140628 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): > debian/rules build > dh build > dh_testdir > dh_auto_configure > Created MYMETA.yml and MYMETA.json > Creating new 'Build' script for 'Mail-SPF' version 'v2.9.0' > dh_auto_build > Building Mail-SPF > dh_auto_test > t/00.00-class-misc.t .......... ok > t/00.01-class-util.t .......... ok > t/00.02-class-request.t ....... ok > t/00.03-class-result.t ........ ok > Unknown error on DNS 'A' lookup of 'example.com' (EDNSError) at > /«PKGBUILDDIR»/blib/lib/Mail/SPF/Server.pm line 573. > # Looks like you planned 23 tests but ran 19. > # Looks like your test exited with 255 just after 19. > t/00.04-class-server.t ........ > Dubious, test returned 255 (wstat 65280, 0xff00) > Failed 4/23 subtests > t/00.05-class-macrostring.t ... ok > t/00.99-class-misc.t .......... ok > t/10.00-rfc4408.t ............. skipped: Mail::SPF::Test required for testing > Mail::SPF's RFC compliance > t/10.01-rfc4406.t ............. skipped: Mail::SPF::Test required for testing > Mail::SPF's RFC compliance > t/90-author-pod-validation.t .. ok > > Test Summary Report > ------------------- > t/00.04-class-server.t (Wstat: 65280 Tests: 19 Failed: 0) > Non-zero exit status: 255 > Parse errors: Bad plan. You planned 23 tests but ran 19. > Files=10, Tests=155, 2 wallclock secs ( 0.08 usr 0.08 sys + 1.34 cusr > 0.25 csys = 1.75 CPU) > Result: FAIL > Failed 1/10 test programs. 0/155 subtests failed. > dh_auto_test: perl Build test returned exit code 255 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/06/28/mail-spf-perl_2.9.0-2_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]
