Skip Menu |

This queue is for tickets about the Test-Valgrind CPAN distribution.

Report information
The Basics
Id: 44969
Status: resolved
Priority: 0/
Queue: Test-Valgrind

People
Owner: Nobody in particular
Requestors: MATEU [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.08
Fixed in: (no value)



Subject: t/20-good.t fail OK or not?
I'm confused by the test failure messages below. The first one "bogus failure" seems to be expected, but then the 'valgrind errors' test failing I don't understand. Is this being reported because of the 'bogus failure' and if so then is it safe to ignore? ------------------------------------------------------------- t/00-load.................1/1 # Testing Test::Valgrind 0.08, Perl 5.010000, /usr/bin/perl t/00-load.................ok t/01-import...............ok t/10-suppressions.........1/3 # 8 suppressions, of which 8 are not empty t/10-suppressions.........ok t/20-good................. # Failed test 'bogus failure, don't worry' # at t/20-good.t line 15. # Looks like you failed 1 test of 1. t/20-good.................1/5 # Failed test 'valgrind errors' # at /root/.cpan/build/Test-Valgrind-0.08-28yzB2/blib/lib/Test/Valgrind.pm line 226. # got: 1 # expected: 0 # Looks like you failed 1 test of 5. # Looks like your test exited with 1 just after 5. t/20-good................. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/5 subtests t/30-bad..................ok t/90-boilerplate..........ok t/91-pod..................ok t/92-pod-coverage.........ok t/95-portability-files....skipped: Test::Portability::Files required for testing filenames portability t/99-kwalitee.............ok Test Summary Report ------------------- t/20-good (Wstat: 256 Tests: 5 Failed: 1) Failed test: 1 Non-zero exit status: 1 t/30-bad (Wstat: 0 Tests: 5 Failed: 0) TODO passed: 2 Files=10, Tests=36, 10 wallclock secs ( 0.04 usr 0.02 sys + 8.57 cusr 0.27 csys = 8.90 CPU) Result: FAIL Failed 1/10 test programs. 1/36 subtests failed.
Hello too, Show quoted text
> I'm confused by the test failure messages below. The first one "bogus > failure" seems to be expected, but then the 'valgrind errors' test > failing I don't understand.
Another test, unrelated with the 'bogus failure', failed. Show quoted text
> Is this being reported because of the > 'bogus failure' and if so then is it safe to ignore?
The anwser to this question depends on your policy towards failing tests, i.e. whether you usually install a module that fails some of its tests. Vincent.
Since this message isn't displayed anymore in the 1.x series, I'm closing this report.