Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Hash-MultiValue CPAN distribution.

Report information
The Basics
Id: 74096
Status: resolved
Priority: 0/
Queue: Hash-MultiValue

People
Owner: Nobody in particular
Requestors: d.thomas [...] its.uq.edu.au
Cc:
AdminCc:

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



Subject: "uninitialized value" in tests
perl 5.14.2, RHEL5 Hash-MultiValue-0.10.tar.gz # make test PERL_DL_NONLAZY=1 /opt/perl/uq.is.perl.rhel5-5.14.2-20120115/bin/perl "- MExtUtils::Command::MM" "-e" "test_harness(0, 'inc', 'blib/lib', 'blib/arch')" t/*.t t/00_compile.t .. ok t/from_mixed.t .. ok t/hash.t ........ ok t/multi.t ....... ok t/ref.t ......... skipped: No UNIVERSAL::ref t/set.t ......... 1/? Use of uninitialized value in numeric eq (==) at /data/opt/uq.local/build/uq.is.perl.rhel5-5.14.2-20120115.build/tarball-build/Hash- MultiValue-0.10/blib/lib/Hash/MultiValue.pm line 110. t/set.t ......... ok t/threads.t ..... skipped: perl interpreter is not compiled with ithreads t/write.t ....... 1/? Use of uninitialized value in numeric eq (==) at /data/opt/uq.local/build/uq.is.perl.rhel5-5.14.2-20120115.build/tarball-build/Hash- MultiValue-0.10/blib/lib/Hash/MultiValue.pm line 110. Use of uninitialized value in numeric eq (==) at /data/opt/uq.local/build/uq.is.perl.rhel5- 5.14.2-20120115.build/tarball-build/Hash-MultiValue-0.10/blib/lib/Hash/MultiValue.pm line 110. t/write.t ....... ok All tests successful. Files=8, Tests=51, 0 wallclock secs ( 0.04 usr 0.02 sys + 0.20 cusr 0.04 csys = 0.30 CPU) Result: PASS those go away (fixed?) by changing line 110 in MultiValue.pm shift @drop, next if @drop && $_ == $drop[0];
I cannot reproduce this. If you use the latest version of HMV, can you?
Subject: Re: [rt.cpan.org #74096] "uninitialized value" in tests
Date: Tue, 7 May 2013 09:29:29 -0700
To: bug-Hash-MultiValue [...] rt.cpan.org
From: Tatsuhiko Miyagawa <miyagawa [...] gmail.com>
Seems it's fixed in 0.12 according to the Changelog :) -- Tatsuhiko Miyagawa
Hooray, another one of those. (I’ve been going through the tickets on my dashboard today and found that many of them are actually long resolved.)