| From: | gregoa [...] cpan.org |
| Subject: | libgeometry-primitive-perl: FTBFS in jessie: Tests failures |
We have the following bug reported to the Debian package of
Geometry-Primitive (https://bugs.debian.org/768735):
It doesn't seem to be a bug in the packaging, so you may want to take
a look. Thanks!
Summary: t/010-serialize.t uses MooseX/Storage / MooseX/Storage/Format/JSON
which since 0.48 requites JSON::MaybeXS insted of JSON::Any.
I suppose the prereqs need an update.
------8<-----------8<-----------8<-----------8<-----------8<-----
From: Lucas Nussbaum <lucas@lucas-nussbaum.net>
To: submit@bugs.debian.org
Subject: libgeometry-primitive-perl: FTBFS in jessie: Tests failures
Date: Sun, 9 Nov 2014 08:26:20 +0100
Source: libgeometry-primitive-perl
Version: 0.24-1
Severity: serious
Tags: jessie sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64
Hi,
During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
Show quoted text
> # Looks like your test exited with 2 before it could output anything.
> t/010-serialize.t ..
> Dubious, test returned 2 (wstat 512, 0x200)
> Failed 7/7 subtests
> t/dimension.t ...... ok
>
> Test Summary Report
> -------------------
> t/010-serialize.t (Wstat: 512 Tests: 0 Failed: 0)
> Non-zero exit status: 2
> Parse errors: Bad plan. You planned 7 tests but ran 0.
> Files=10, Tests=58, 3 wallclock secs ( 0.05 usr 0.05 sys + 2.59 cusr 0.24 csys = 2.93 CPU)
> Result: FAIL
> Failed 1/10 test programs. 0/58 subtests failed.
> make[1]: *** [test_dynamic] Error 255
> Makefile:815: recipe for target 'test_dynamic' failed
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/11/08/libgeometry-primitive-perl_0.24-1_jessie.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.
------8<-----------8<-----------8<-----------8<-----------8<-----
Thanks for considering,
gregor herrmann,
Debian Perl Group