Bug#832833: libtest-valgrind-perl: FTBFS: Tests failures
gregor herrmann
gregoa at debian.org
Sat Jul 30 16:52:19 UTC 2016
On Fri, 29 Jul 2016 14:15:07 -0300, Vincent Pit (VPIT) wrote:
> Hi, upstream speaking.
Thanks for joining :)
> > The full build log is available from:
> > http://people.debian.org/~lucas/logs/2016/07/28/libtest-valgrind-perl_1.18-2_unstable.log
> Can you tell me the output of "valgrind --version" on your system?
> If, as I suspect, this output now ends with a full stop,
Not really:
% valgrind --version
valgrind-3.12.0.SVN
> then you might want
> to try giving a shot at the changes I pushed at :
> http://git.profvince.com/?p=perl/modules/Test-Valgrind.git;a=summary
When I run the failing test manually in chroot I get:
# prove --blib --verbose t/20-bad.t
t/20-bad.t .. # Using valgrind 3.1.0 located at /usr/bin/valgrind
# Generating suppressions...
Found 18 distinct suppressions
# Suppressions for this perl stored in /home/gregoa/.perl/Test-Valgrind/suppressions/1.18/memcheck-3.1.0-226083a99e06b327ea9404c90c48bd39.supp
# Using suppressions from /home/gregoa/.perl/Test-Valgrind/suppressions/1.18/memcheck-3.1.0-226083a99e06b327ea9404c90c48bd39.supp
1..18
# valgrind: Bad option: --xml=yes, but no XML destination specified
# valgrind: --xml=yes has been specified, but there is no XML output
# valgrind: destination. You must specify an XML output destination
# valgrind: using --xml-fd, --xml-file or --xml-socket.
# valgrind: Use --help for more information or consult the user manual.
ok 1 - InvalidFree
ok 2 - MismatchedFree
ok 3 - InvalidRead
ok 4 - InvalidWrite
ok 5 - InvalidJump
ok 6 - Overlap
ok 7 - InvalidMemPool
ok 8 - UninitCondition
ok 9 - UninitValue
ok 10 - SyscallParam
ok 11 - ClientCheck
ok 12 - Leak_DefinitelyLost
ok 13 - Leak_IndirectlyLost
ok 14 - Leak_PossiblyLost
ok 15 - Leak_StillReachable
#
# no element found at line 1, column 0, byte 0 at /usr/lib/x86_64-linux-gnu/perl5/5.22/XML/Parser.pm line 187.
# at /build/libtest-valgrind-perl-1.18/blib/lib/Test/Valgrind/Session.pm line 390.
not ok 16 - caught one extra leak
# Failed test 'caught one extra leak'
# at /build/libtest-valgrind-perl-1.18/blib/lib/Test/Valgrind.pm line 378.
# got: '0'
# expected: '1'
not ok 17 - no extra leak caught, hence no bytes leaked
# Failed test 'no extra leak caught, hence no bytes leaked'
# at /build/libtest-valgrind-perl-1.18/blib/lib/Test/Valgrind.pm line 378.
not ok 18 - no extra leak caught, hence no block leaked
# Failed test 'no extra leak caught, hence no block leaked'
# at /build/libtest-valgrind-perl-1.18/blib/lib/Test/Valgrind.pm line 378.
# Looks like you failed 3 tests of 18.
Dubious, test returned 3 (wstat 768, 0x300)
Failed 3/18 subtests
Test Summary Report
-------------------
t/20-bad.t (Wstat: 768 Tests: 18 Failed: 3)
Failed tests: 16-18
Non-zero exit status: 3
Files=1, Tests=18, 3 wallclock secs ( 0.03 usr 0.00 sys + 2.94 cusr 0.04 csys = 3.01 CPU)
Result: FAIL
Cheers,
gregor
--
.''`. Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/
`. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
`- NP: Dire Straits: Walk Of Live
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: Digital Signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20160730/49367ff5/attachment.sig>
More information about the pkg-perl-maintainers
mailing list