Skip Menu |

This queue is for tickets about the Filter-Crypto CPAN distribution.

Report information
The Basics
Id: 131973
Status: resolved
Priority: 0/
Queue: Filter-Crypto

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

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



Subject: Undefined subroutine &Foo::foo called
The test suite fails on some of my smoker systems: ... Undefined subroutine &Foo::foo called at foo.pl line 3. # Failed test '... and encrypted module runs OK with Carp loaded' # at t/02_function.t line 786. # got: '' # expected: 'Hello, world.' # Looks like you failed 1 test of 295. t/02_function.t ...... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/295 subtests Undefined subroutine &Foo::foo called at foo.pl line 3. # Failed test '... and encrypted script + unencrypted module run OK' # at t/03_script.t line 443. # got: '' # expected: 'Hello, world.' ... (etc) ... It seems that this happens if a module Foo.pm is installed. Maybe it's more safe to use a dummy module name in a namespace you control, e.g. Filter::Crypto::Foo or so.
On Wed Feb 26 01:44:18 2020, SREZIC wrote: Show quoted text
> The test suite fails on some of my smoker systems: > > ... > Undefined subroutine &Foo::foo called at foo.pl line 3. > > # Failed test '... and encrypted module runs OK with Carp loaded' > # at t/02_function.t line 786. > # got: '' > # expected: 'Hello, world.' > # Looks like you failed 1 test of 295. > t/02_function.t ...... > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/295 subtests > Undefined subroutine &Foo::foo called at foo.pl line 3. > > # Failed test '... and encrypted script + unencrypted module run OK' > # at t/03_script.t line 443. > # got: '' > # expected: 'Hello, world.' > ... (etc) ... > > It seems that this happens if a module Foo.pm is installed. Maybe it's > more safe to use a dummy module name in a namespace you control, e.g. > Filter::Crypto::Foo or so.
Thanks for spotting this and suggesting a solution. I have fixed this in commit e8e4cf554e, which will be in release 2.09 - hopefully soon.
Thanks again. This is now fixed in 2.09, released yesterday.