Bug#682633: libemail-outlook-message-perl: FTBFS: test failed

[Lucas Nussbaum]

Source: libemail-outlook-message-perl
Version: 0.911-1
Severity: serious
Tags: wheezy sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20120724 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> dh build
>    dh_testdir
>    dh_auto_configure
> Checking prerequisites...
>   requires:
>     !  IO::All is not installed
> 
> ERRORS/WARNINGS FOUND IN PREREQUISITES.  You may wish to install the versions
> of the modules indicated above before proceeding with this installation
> 
> Run 'Build installdeps' to install missing prerequisites.
> 
> Created MYMETA.yml and MYMETA.json
> Creating new 'Build' script for 'Email-Outlook-Message' version '0.911'
>    dh_auto_build
> Building Email-Outlook-Message
>    dh_auto_test
> t/basics.t ............... ok
> t/gpg_signed.t ........... ok
> 
> #   Failed test at t/internals.t line 87.
> #          got: 'plain

> # '
> #     expected: 'plain
> # '
> 
> #   Failed test at t/internals.t line 88.
> #          got: 'html

> # '
> #     expected: 'html
> # '
> # Looks like you failed 2 tests of 17.
> t/internals.t ............ 
> Dubious, test returned 2 (wstat 512, 0x200)
> Failed 2/17 subtests 
> 
> #   Failed test 'No body'
> #   at t/plain_jpeg_attached.t line 17.
> #          got: '

> # '
> #     expected: '
> # '
> 
> #   Failed test 'Testing body'
> #   at t/plain_jpeg_attached.t line 29.
> #          got: 'test
> # 

> # '
> #     expected: 'test
> # 
> # '
> # Looks like you failed 2 tests of 23.
> t/plain_jpeg_attached.t .. 
> Dubious, test returned 2 (wstat 512, 0x200)
> Failed 2/23 subtests 
> 
> #   Failed test 'Check body'
> #   at t/plain_uc_unsent.t line 23.
> #          got: 'This is a test
> # The body is in plain text

> # '
> #     expected: 'This is a test
> # The body is in plain text
> # '
> # Looks like you failed 1 test of 15.
> t/plain_uc_unsent.t ...... 
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/15 subtests 
> 
> #   Failed test 'Check body'
> #   at t/plain_uc_wc_unsent.t line 28.
> Wide character in print at /usr/share/perl/5.14/Test/Builder.pm line 1759.
> #          got: 'This is a test
> # The body is in p汬ain text

> # '
> #     expected: 'This is a test
> # The body is in p汬ain text
> # '
> # Looks like you failed 1 test of 14.
> t/plain_uc_wc_unsent.t ... 
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/14 subtests 
> 
> #   Failed test 'Check body'
> #   at t/plain_unsent.t line 25.
> #          got: 'This is a test
> # The body is in plain text

> # '
> #     expected: 'This is a test
> # The body is in plain text
> # '
> # Looks like you failed 1 test of 15.
> t/plain_unsent.t ......... 
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/15 subtests 
> t/pod_coverage.t ......... ok
> 
> Test Summary Report
> -------------------
> t/internals.t          (Wstat: 512 Tests: 17 Failed: 2)
>   Failed tests:  16-17
>   Non-zero exit status: 2
> t/plain_jpeg_attached.t (Wstat: 512 Tests: 23 Failed: 2)
>   Failed tests:  9, 15
>   Non-zero exit status: 2
> t/plain_uc_unsent.t    (Wstat: 256 Tests: 15 Failed: 1)
>   Failed test:  10
>   Non-zero exit status: 1
> t/plain_uc_wc_unsent.t (Wstat: 256 Tests: 14 Failed: 1)
>   Failed test:  10
>   Non-zero exit status: 1
> t/plain_unsent.t       (Wstat: 256 Tests: 15 Failed: 1)
>   Failed test:  11
>   Non-zero exit status: 1
> Files=8, Tests=91,  1 wallclock secs ( 0.23 usr  0.10 sys +  0.64 cusr  0.16 csys =  1.13 CPU)
> Result: FAIL
> Failed 5/8 test programs. 7/91 subtests failed.
> dh_auto_test: perl Build test returned exit code 255
> make: *** [build] Error 255

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/07/24/libemail-outlook-message-perl_0.911-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.