Bug#730913: libmongodb-perl: FTBFS: Failed tests

[David Suárez]

Source: libmongodb-perl
Version: 0.702.1+ds-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20131128 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[2]: Entering directory `/«BUILDDIR»/libmongodb-perl-0.702.1+ds'
> PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'inc', 'blib/lib', 'blib/arch')" t/*.t t/threads/*.t
> t/bson.t ............ ok
> t/collection.t ...... ok
> t/connection.t ...... ok
> t/cursor.t .......... ok
> t/database.t ........ ok
> 
> #   Failed test 'js err'
> #   at t/db.t line 52.
> #                   'exception: SyntaxError: Unexpected string'
> #     doesn't match '(?^:(?:compile|execution) failed)'
> # Looks like you failed 1 test of 10.
> t/db.t .............. 
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/10 subtests 
> t/dbref.t ........... ok
> t/delegation.t ...... ok
> t/dt_types.t ........ ok
> t/fsync.t ........... ok
> t/gridfs.t .......... ok
> t/regex.t ........... ok
> t/threads/basic.t ... ok
> t/threads/cursor.t .. ok
> t/threads/oid.t ..... ok
> t/types.t ........... ok
> t/w.t ............... ok
> 
> Test Summary Report
> -------------------
> t/db.t            (Wstat: 256 Tests: 10 Failed: 1)
>   Failed test:  9
>   Non-zero exit status: 1
> Files=17, Tests=581, 21 wallclock secs ( 0.18 usr  0.10 sys + 15.05 cusr  1.76 csys = 17.09 CPU)
> Result: FAIL
> Failed 1/17 test programs. 1/581 subtests failed.
> make[2]: *** [test_dynamic] Error 255
> make[2]: Leaving directory `/«BUILDDIR»/libmongodb-perl-0.702.1+ds'
> dh_auto_test: make -j1 test returned exit code 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/11/28/libmongodb-perl_0.702.1+ds-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.