Bug#687403: libio-async-loop-epoll-perl: FTBFS: test failed

[Lucas Nussbaum]

Source: libio-async-loop-epoll-perl
Version: 0.12-1
Severity: serious
Tags: wheezy sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20120912 qa-ftbfs
Justification: FTBFS in wheezy on amd64

Hi,

[ It seems that the fix for #680790 was not applied to
libio-async-loop-epoll-perl ? Or is it only because the fixed
libio-async-perl did not reach testing? ]

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

Relevant part:
>  debian/rules build
> dh build
>    dh_testdir
>    dh_auto_configure
> Created MYMETA.yml and MYMETA.json
> Creating new 'Build' script for 'IO-Async-Loop-Epoll' version '0.12'
>    dh_auto_build
> Building IO-Async-Loop-Epoll
>    dh_auto_test
> t/00use.t ........... ok
> t/01loop-io.t ....... ok
> 
> #   Failed test 'One ->loop_once(1) sufficient for a single 0.1 second timer'
> #   at /usr/share/perl5/IO/Async/LoopTests.pm line 484.
> #          got: '2'
> #     expected: '1'
> # Looks like you failed 1 test of 26.
> t/02loop-timer.t .... 
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/26 subtests 
> t/03loop-signal.t ... ok
> t/04loop-idle.t ..... ok
> t/05loop-child.t .... ok
> t/06loop-control.t .. ok
> t/99pod.t ........... ok
> 
> Test Summary Report
> -------------------
> t/02loop-timer.t  (Wstat: 256 Tests: 26 Failed: 1)
>   Failed test:  20
>   Non-zero exit status: 1
> Files=8, Tests=105, 16 wallclock secs ( 0.06 usr  0.04 sys +  0.51 cusr  0.15 csys =  0.76 CPU)
> Result: FAIL
> Failed 1/8 test programs. 1/105 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/09/12/libio-async-loop-epoll-perl_0.12-1_wheezy.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.