Bug#746093: libwww-mechanize-treebuilder-perl: FTBFS: Tests failures

[David Suárez]

Source: libwww-mechanize-treebuilder-perl
Version: 1.10003-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20140426 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):
>
> 	MooseX::Role::Parameterized::Meta::Role::Parameterizable::construct_parameters('MooseX::Role::Parameterized::Meta::Role::Parameterizable=HASH...', 'tree_class', 'HTML::TreeBuilder::XPath') called at /usr/share/perl5/MooseX/Role/Parameterized/Meta/Role/Parameterizable.pm line 55
> 	MooseX::Role::Parameterized::Meta::Role::Parameterizable::generate_role('MooseX::Role::Parameterized::Meta::Role::Parameterizable=HASH...', 'consumer', 'MockMechanize=HASH(0x42cca38)', 'parameters', 'HASH(0x3820eb8)') called at /usr/share/perl5/MooseX/Role/Parameterized/Meta/Role/Parameterizable.pm line 105
> 	MooseX::Role::Parameterized::Meta::Role::Parameterizable::apply('MooseX::Role::Parameterized::Meta::Role::Parameterizable=HASH...', 'MockMechanize=HASH(0x42cca38)', 'tree_class', 'HTML::TreeBuilder::XPath') called at t/03-xpath.t line 21
> Failed 1/3 test programs. 0/22 subtests failed.
> t/03-xpath.t ......... ok
> 
> Test Summary Report
> -------------------
> t/02-parameterize.t (Wstat: 65280 Tests: 2 Failed: 0)
>   Non-zero exit status: 255
>   Parse errors: Bad plan.  You planned 9 tests but ran 2.
> Files=3, Tests=22,  2 wallclock secs ( 0.04 usr  0.03 sys +  1.59 cusr  0.28 csys =  1.94 CPU)
> Result: FAIL
> make[1]: *** [test_dynamic] Error 255
> make[1]: 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/04/26/libwww-mechanize-treebuilder-perl_1.10003-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.