Bug #117284 for Loop-Flow-Object: pod coverage and pod test fail

Mon Aug 29 02:20:35 2016 SREZIC [...] cpan.org - Ticket created

Subject:

pod coverage and pod test fail

See subject. Test log: ... # Failed test 'Pod coverage on Loop::Flow::Object' # at /opt/perl-5.25.4/lib/site_perl/5.25.4/Test/Pod/Coverage.pm line 133. # Coverage for Loop::Flow::Object is 60.0%, with 2 naked subroutines: # check_child # start_main # Looks like you failed 1 test of 1. t/pod-coverage.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests # Failed test 'POD test for blib/lib/Loop/Flow/Object.pm' # at /opt/perl-5.25.4/lib/site_perl/5.25.4/Test/Pod.pm line 187. # blib/lib/Loop/Flow/Object.pm (224): You forgot a '=back' before '=head1' # Looks like you failed 1 test of 1. t/pod.t ........... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests ...

Mon Aug 29 13:16:06 2016 ether [...] cpan.org - Correspondence added

On 2016-08-28 23:20:35, SREZIC wrote: Show quoted text

> See subject. Test log: > > ... > # Failed test 'Pod coverage on Loop::Flow::Object' > # at /opt/perl-5.25.4/lib/site_perl/5.25.4/Test/Pod/Coverage.pm line 133. > # Coverage for Loop::Flow::Object is 60.0%, with 2 naked subroutines: > # check_child > # start_main > # Looks like you failed 1 test of 1. > t/pod-coverage.t .. > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/1 subtests > > # Failed test 'POD test for blib/lib/Loop/Flow/Object.pm' > # at /opt/perl-5.25.4/lib/site_perl/5.25.4/Test/Pod.pm line 187. > # blib/lib/Loop/Flow/Object.pm (224): You forgot a '=back' before '=head1' > # Looks like you failed 1 test of 1. > t/pod.t ........... > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/1 subtests > ...

While this test failure is indeed an issue that should be corrected, please don't allow pod, critic 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 Aug 29 13:16:06 2016 The RT System itself - Status changed from 'new' to 'open'