Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Devel-ebug CPAN distribution.

Report information
The Basics
Id: 33009
Status: resolved
Priority: 0/
Queue: Devel-ebug

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

Bug Information
Severity: Normal
Broken in: 0.48
Fixed in: 0.50



Subject: bleadperl@33022 affects stack test
You are in goo company, Params-Validate-1.15 had a similar test that expected 0 and got '' for false. t/stack............ # Failed test at t/stack.t line 26. # got: '' # expected: '0' # Looks like you failed 1 test of 29. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/29 subtests Test Summary Report ------------------- t/stack.t (Wstat: 256 Tests: 29 Failed: 1) Failed test: 6 Non-zero exit status: 1 Files=19, Tests=266, 64 wallclock secs ( 0.36 usr 0.04 sys + 29.48 cusr 1.82 c sys = 31.70 CPU) Result: FAIL This is due to Change 33022 by nicholas@nicholas-saigo on 2008/01/21 09:04:54 Change the wantarray result from caller from IV to bool for the SCALAR/ ARRAY case. This doesn't contradict the documentation, as there isn't any. Oops. Oops;)
This has (hopefully) been fixed in the latest release (0.50). Thanks, --Brock On Fri Feb 08 02:59:42 2008, ANDK wrote: Show quoted text
> You are in goo company, Params-Validate-1.15 had a similar test that > expected 0 and got '' for false. > > t/stack............ > # Failed test at t/stack.t line 26. > # got: '' > # expected: '0' > # Looks like you failed 1 test of 29. > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/29 subtests > > Test Summary Report > ------------------- > t/stack.t (Wstat: 256 Tests: 29 Failed: 1) > Failed test: 6 > Non-zero exit status: 1 > Files=19, Tests=266, 64 wallclock secs ( 0.36 usr 0.04 sys + 29.48 cusr > 1.82 c > sys = 31.70 CPU) > Result: FAIL > > > This is due to > > Change 33022 by nicholas@nicholas-saigo on 2008/01/21 09:04:54 > > Change the wantarray result from caller from IV to bool for the SCALAR/ > ARRAY case. This doesn't contradict the documentation, as there isn't > any. Oops. > > > > Oops;)