Bug #117807 for Storage-Nexsan-NMP: pod test fails (encoding problem)

Mon Sep 12 16:40:09 2016 SREZIC [...] cpan.org - Ticket created

Subject:

pod test fails (encoding problem)

See subject. Test log: # Failed test 'POD test for blib/lib/Storage/Nexsan/README.pod' # at /usr/perl5.24.1-RC3p/lib/site_perl/5.24.1/Test/Pod.pm line 187. Wide character in print at /usr/perl5.24.1-RC3p/lib/site_perl/5.24.1/Test2/Formatter/TAP.pm line 105. # blib/lib/Storage/Nexsan/README.pod (171): Non-ASCII character seen before =encoding in '(âHEALTHYâ,'. Assuming UTF-8 # Failed test 'POD test for blib/lib/Storage/Nexsan/NMP.pm' # at /usr/perl5.24.1-RC3p/lib/site_perl/5.24.1/Test/Pod.pm line 187. Wide character in print at /usr/perl5.24.1-RC3p/lib/site_perl/5.24.1/Test2/Formatter/TAP.pm line 105. # blib/lib/Storage/Nexsan/NMP.pm (380): Non-ASCII character seen before =encoding in '(âHEALTHYâ,'. Assuming UTF-8 # Looks like you failed 2 tests of 2. t/pod.t ........... Dubious, test returned 2 (wstat 512, 0x200) Failed 2/2 subtests

Mon Sep 12 16:57:11 2016 ether [...] cpan.org - Correspondence added

On 2016-09-12 13:40:09, SREZIC wrote: Show quoted text

> See subject. Test log: > > > # Failed test 'POD test for blib/lib/Storage/Nexsan/README.pod' > # at /usr/perl5.24.1-RC3p/lib/site_perl/5.24.1/Test/Pod.pm line 187. > Wide character in print at /usr/perl5.24.1- > RC3p/lib/site_perl/5.24.1/Test2/Formatter/TAP.pm line 105. > # blib/lib/Storage/Nexsan/README.pod (171): Non-ASCII character seen > before =encoding in '(âHEALTHYâ,'. Assuming UTF-8 > > # Failed test 'POD test for blib/lib/Storage/Nexsan/NMP.pm' > # at /usr/perl5.24.1-RC3p/lib/site_perl/5.24.1/Test/Pod.pm line 187. > Wide character in print at /usr/perl5.24.1- > RC3p/lib/site_perl/5.24.1/Test2/Formatter/TAP.pm line 105. > # blib/lib/Storage/Nexsan/NMP.pm (380): Non-ASCII character seen > before =encoding in '(âHEALTHYâ,'. Assuming UTF-8 > # Looks like you failed 2 tests of 2. > t/pod.t ........... > Dubious, test returned 2 (wstat 512, 0x200) > Failed 2/2 subtests

While this test failure is indeed an issue that should be corrected, please don't allow pod, critic, coverage or kwalitee tests to run for normal user installs, as they make the installation fail unnecessarily when newer versions of the tester module introduces errors that you cannot anticipate. Also spelling tests are dependent on what dictionaries are installed locally, and critic tests use all plugins that are installed, neither of which can be predicted in advance. Either move these tests to xt/, or guard them with: plan skip_all => "These tests are for authors only!" unless $ENV{AUTHOR_TESTING} or $ENV{RELEASE_TESTING};

Mon Sep 12 16:57:12 2016 The RT System itself - Status changed from 'new' to 'open'