Source: libmonitoring-availability-perl
Version: 0.46-1
Severity: serious
Tags: stretch sid
User: [email protected]
Usertags: qa-ftbfs-20161001 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):
> t/32-availability-service.t                   (Wstat: 3328 Tests: 18 Failed: 
> 13)
>   Failed tests:  4-8, 10-17
>   Non-zero exit status: 13
> t/33-availability-service_ok_logs.t           (Wstat: 13312 Tests: 63 Failed: 
> 52)
>   Failed tests:  4-7, 9-20, 23-27, 29-41, 44-48, 50-62
>   Non-zero exit status: 52
> t/34-availability-breakdown.t                 (Wstat: 512 Tests: 4 Failed: 2)
>   Failed tests:  3-4
>   Non-zero exit status: 2
> t/35-availability-timeperiods.t               (Wstat: 5376 Tests: 30 Failed: 
> 21)
>   Failed tests:  4-6, 8-13, 17-19, 21-29
>   Non-zero exit status: 21
> Files=25, Tests=245,  0 wallclock secs ( 0.09 usr  0.00 sys +  0.78 cusr  
> 0.04 csys =  0.91 CPU)
> Result: FAIL
> Failed 6/25 test programs. 111/245 subtests failed.
> Makefile:759: recipe for target 'test_dynamic' failed

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   
http://aws-logs.debian.net/2016/10/01/libmonitoring-availability-perl_0.46-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.

Reply via email to