Skip Menu |

This queue is for tickets about the Log-Sentry CPAN distribution.

Report information
The Basics
Id: 116706
Status: open
Priority: 0/
Queue: Log-Sentry

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

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



Subject: pod coverage test fails
If Test::Pod::Coverage is available: # Failed test 'Pod coverage on Log::Sentry' # at /opt/perl-5.24.1-RC2/lib/site_perl/5.24.1/Test/Pod/Coverage.pm line 133. # Coverage for Log::Sentry is 66.7%, with 1 naked subroutine: # buildMessage # Looks like you failed 1 test of 1. t/pod-coverage.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests
On 2016-08-03 23:52:51, SREZIC wrote: Show quoted text
> If Test::Pod::Coverage is available: > > # Failed test 'Pod coverage on Log::Sentry' > # at /opt/perl-5.24.1-RC2/lib/site_perl/5.24.1/Test/Pod/Coverage.pm > line 133. > # Coverage for Log::Sentry is 66.7%, with 1 naked subroutine: > # buildMessage > # Looks like you failed 1 test of 1. > t/pod-coverage.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, both of which cannot be predicted in advance. Either move them to xt/, or guard them with: plan skip_all => "These tests are for authors only!" unless $ENV{AUTHOR_TESTING} or $ENV{RELEASE_TESTING};