Bug#852889: liblatex-driver-perl: FTBFS: Test failures

[Lucas Nussbaum]

Source: liblatex-driver-perl
Version: 0.300.2-1
Severity: serious
Tags: stretch sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20170128 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):
> ok 9 - should not have run makeindex
> ok
> t/90-kwalitee.t ............. skipped: Author test.  Set $ENV{TEST_AUTHOR} to a true value to run.
> t/91-pod.t .................. skipped: Author test.  Set $ENV{TEST_AUTHOR} to a true value to run.
> t/92-pod-coverage.t ......... skipped: Author test.  Set $ENV{TEST_AUTHOR} to a true value to run.
> t/93-perl-critic.t .......... skipped: Author test.  Set $ENV{TEST_AUTHOR} to a true value to run.
> 
> Test Summary Report
> -------------------
> t/10-simpledoc.t          (Wstat: 256 Tests: 8 Failed: 0)
>   Non-zero exit status: 1
>   Parse errors: Bad plan.  You planned 24 tests but ran 8.
> Files=17, Tests=106,  2 wallclock secs ( 0.07 usr  0.02 sys +  1.74 cusr  0.36 csys =  2.19 CPU)
> Result: FAIL
> Failed 1/17 test programs. 0/106 subtests failed.
> Makefile:800: recipe for target 'test_dynamic' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/01/28/liblatex-driver-perl_0.300.2-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.