Bug#730898: libmoosex-app-cmd-perl: FTBFS: Failed tests

[David Suárez]

Source: libmoosex-app-cmd-perl
Version: 0.07-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20131128 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[1]: Entering directory `/«PKGBUILDDIR»'
> PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
> t/00-load.t ............. ok
> 
> #   Failed test 'got correct list of registered command names'
> #   at t/basic.t line 16.
> #     Structures begin differing at:
> #          $got->[1] = '--version'
> #     $expected->[1] = '-?'
> 
> #   Failed test 'got correct list of registered command plugins'
> #   at t/basic.t line 24.
> #     Structures begin differing at:
> #          $got->[2] = 'App::Cmd::Command::version'
> #     $expected->[2] = 'Test::MyCmd::Command::bark'
> # Looks like you failed 2 tests of 12.
> t/basic.t ............... 
> Dubious, test returned 2 (wstat 512, 0x200)
> Failed 2/12 subtests 
> t/build_emulates_new.t .. ok
> t/configfile.t .......... skipped: These tests require MooseX::ConfigFromFile and YAML
> 
> Test Summary Report
> -------------------
> t/basic.t             (Wstat: 512 Tests: 12 Failed: 2)
>   Failed tests:  2-3
>   Non-zero exit status: 2
> Files=4, Tests=15,  2 wallclock secs ( 0.04 usr  0.03 sys +  1.42 cusr  0.15 csys =  1.64 CPU)
> Result: FAIL
> Failed 1/4 test programs. 2/15 subtests failed.
> 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/2013/11/28/libmoosex-app-cmd-perl_0.07-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.