Skip Menu |

This queue is for tickets about the MikroTik-API CPAN distribution.

Report information
The Basics
Id: 130171
Status: open
Priority: 0/
Queue: MikroTik-API
People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: 1.1.0
Fixed in: (no value)

History Show all quoted text
  Thu Jul 25 12:19:52 2019 SREZIC [...] cpan.org - Ticket created
Subject: t/pod-coverage.t fails (on some systems)
On some of my smoker systems the pod coverage test fails: ... # Failed test 'Pod coverage on MikroTik::API' # at /usr/perl5.18.2/lib/site_perl/5.18.2/Test/Pod/Coverage.pm line 133. # Coverage for MikroTik::API is 75.0%, with 3 naked subroutines: # SO_KEEPALIVE # SO_RCVTIMEO # SO_SNDTIMEO # Looks like you failed 1 test of 1. t/pod-coverage.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests ...
  Thu Jul 25 12:21:23 2019 SREZIC [...] cpan.org - Correspondence added
On 2019-07-25 12:19:52, SREZIC wrote: Show quoted text
> On some of my smoker systems the pod coverage test fails: > > ... > # Failed test 'Pod coverage on MikroTik::API' > # at /usr/perl5.18.2/lib/site_perl/5.18.2/Test/Pod/Coverage.pm line 133. > # Coverage for MikroTik::API is 75.0%, with 3 naked subroutines: > # SO_KEEPALIVE > # SO_RCVTIMEO > # SO_SNDTIMEO > # Looks like you failed 1 test of 1. > t/pod-coverage.t .. > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/1 subtests > ...
It seems that mostly older perls are affected (5.12 .. 5.18).
  Thu Jul 25 16:54:55 2019 ether [...] cpan.org - Correspondence added
On 2019-07-25 09:19:52, SREZIC wrote: Show quoted text
> On some of my smoker systems the pod coverage test fails:
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};
  Thu Jul 25 16:54:56 2019 The RT System itself - Status changed from 'new' to 'open'