Bug#743097: libconfig-model-itself-perl: FTBFS: Tests failures

[David Suárez]

Source: libconfig-model-itself-perl
Version: 1.239-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20140329 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»'
> xvfb-run -a dh_auto_test 
> t/backend_detect.t ......... ok
> t/dot_graph.t .............. ok
> t/itself-editor.t .......... ok
> 
> #   Failed test 'Compared the 2 full dumps'
> #   at t/itself.t line 191.
> #     Structures begin differing at:
> #          $got->[3] = '  author:=dod at foo'
> #     $expected->[3] = '  author:=dod at foo.com'
> 
> #   Failed test 'Compared the 3rd full dump with first one'
> #   at t/itself.t line 208.
> #     Structures begin differing at:
> #          $got->[3] = '  author:=dod at foo'
> #     $expected->[3] = '  author:=dod at foo.com'
> # Looks like you failed 2 tests of 19.
> t/itself.t ................. 
> Dubious, test returned 2 (wstat 512, 0x200)
> Failed 2/19 subtests 
> t/itself_snippet.t ......... ok
> t/list_itself_structure.t .. ok
> t/load_write_itself.t ...... ok
> t/pod.t .................... ok
> t/pod_gen.t ................ ok
> t/release-pod-syntax.t ..... skipped: these tests are for release candidate testing
> 
> Test Summary Report
> -------------------
> t/itself.t               (Wstat: 512 Tests: 19 Failed: 2)
>   Failed tests:  12, 14
>   Non-zero exit status: 2
> Files=10, Tests=98, 80 wallclock secs ( 0.08 usr  0.07 sys + 65.22 cusr  1.35 csys = 66.72 CPU)
> Result: FAIL
> Failed 1/10 test programs. 2/98 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/03/29/libconfig-model-itself-perl_1.239-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.