Skip Menu |

This queue is for tickets about the Module-Util CPAN distribution.

Report information
The Basics
Id: 77500
Status: resolved
Priority: 0/
Queue: Module-Util

People
Owner: Nobody in particular
Requestors: zefram [...] fysh.org
Cc:
AdminCc:

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



Subject: Module::Util pod not ok
Date: Mon, 28 May 2012 12:48:15 +0100
To: bug-Module-Util [...] rt.cpan.org
From: Zefram <zefram [...] fysh.org>
Running Build test t/01..module.t .. ok t/99..pod.t ..... 1/3 # Failed test 'Module::Util pod ok' # at t/99..pod.t line 21. # /opt/perl-5.12.4/cpan/build/Module-Util-1.07-0X6R_d/lib/Module/Util.pm (399): Non-ASCII character seen before =encoding in 'Kühne'. Assuming UTF-8 # Looks like you failed 1 test of 3. t/99..pod.t ..... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/3 subtests -zefram
On Mon May 28 07:48:29 2012, zefram@fysh.org wrote: Show quoted text
> Running Build test > t/01..module.t .. ok > t/99..pod.t ..... 1/3 > # Failed test 'Module::Util pod ok' > # at t/99..pod.t line 21. > # /opt/perl-5.12.4/cpan/build/Module-Util-1.07- > 0X6R_d/lib/Module/Util.pm (399): Non-ASCII character seen before > =encoding in 'Kühne'. Assuming UTF-8 > # Looks like you failed 1 test of 3. > t/99..pod.t ..... Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/3 subtests >
I've seen the same error from cpan testers too, I can't replicate it myself. Do you know where this string originates? I think the solution might just be to change this test to be author only.
On Mon May 28 08:00:19 2012, MATTLAW wrote: Show quoted text
> On Mon May 28 07:48:29 2012, zefram@fysh.org wrote: > > I've seen the same error from cpan testers too, I can't replicate it > myself. Do you know where this string originates?
Ah. I didn't spot that it was in the THANKS section. I started getting the error after I upgraded Pod::Simple and its dependencies. Show quoted text
> > I think the solution might just be to change this test to be author only.
Actually, this has flagged up something that might have been a real life problem with the module, assuming a similar error was emitted by perldoc. So I'll just add an explicit encoding and leave the test in.