Bug #124442 for POE-Filter-SSL: Pod & Pod coverage tests fail

Thu Feb 15 13:46:10 2018 SREZIC [...] cpan.org - Ticket created

Subject:

Pod & Pod coverage tests fail

See subject. Test log: ... # Failed test 'Pod coverage on POE::Filter::SSL' # at /usr/perl5.26.1p/lib/site_perl/5.26.1/Test/Pod/Coverage.pm line 133. # Coverage for POE::Filter::SSL is 93.3%, with 2 naked subroutines: # POE_FILTER_SSL_get_ex_data_X509_STORE_CTX_idx # POE_FILTER_verify_serial_against_crl_file # Looks like you failed 1 test of 2. t/pod-coverage.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/2 subtests # Failed test 'POD test for blib/lib/POE/Filter/SSL/PreFilter.pm' # at /usr/perl5.26.1p/lib/site_perl/5.26.1/Test/Pod.pm line 187. # blib/lib/POE/Filter/SSL/PreFilter.pm (105): =back without =over # Looks like you failed 1 test of 2. t/pod.t ........... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/2 subtests ...

Fri Feb 16 01:47:34 2018 ether [...] cpan.org - Correspondence added

On 2018-02-15 10:46:10, SREZIC wrote: Show quoted text

> See subject. Test log: > > ... > # Failed test 'Pod coverage on POE::Filter::SSL'

Show quoted text

> # Failed test 'POD test for blib/lib/POE/Filter/SSL/PreFilter.pm'

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};

Fri Feb 16 01:47:34 2018 The RT System itself - Status changed from 'new' to 'open'