Skip Menu |

This queue is for tickets about the LPDS CPAN distribution.

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

History Show all quoted text
  Wed Aug 31 18:45:52 2016 SREZIC [...] cpan.org - Ticket created
Subject: pod coverage test fails (missing pods)
Test suite fails: # Failed test 'Pod coverage on LPDS::Util' # at /opt/perl-5.25.4/lib/site_perl/5.25.4/Test/Pod/Coverage.pm line 133. # LPDS::Util: couldn't find pod # Failed test 'Pod coverage on LPDS::RendererModel' # at /opt/perl-5.25.4/lib/site_perl/5.25.4/Test/Pod/Coverage.pm line 133. # LPDS::RendererModel: couldn't find pod # Failed test 'Pod coverage on LPDS::RendererAxis' # at /opt/perl-5.25.4/lib/site_perl/5.25.4/Test/Pod/Coverage.pm line 133. # LPDS::RendererAxis: couldn't find pod # Failed test 'Pod coverage on LPDS::Renderer' # at /opt/perl-5.25.4/lib/site_perl/5.25.4/Test/Pod/Coverage.pm line 133. # LPDS::Renderer: couldn't find pod # Looks like you failed 4 tests of 5. t/pod-coverage.t .. Dubious, test returned 4 (wstat 1024, 0x400) Failed 4/5 subtests
  Thu Sep 01 02:12:36 2016 ether [...] cpan.org - Correspondence added
On 2016-08-31 15:45:52, SREZIC wrote: Show quoted text
> Test suite fails: > > # Failed test 'Pod coverage on LPDS::Util' > # at /opt/perl-5.25.4/lib/site_perl/5.25.4/Test/Pod/Coverage.pm line 133. > # LPDS::Util: couldn't find pod > > # Failed test 'Pod coverage on LPDS::RendererModel' > # at /opt/perl-5.25.4/lib/site_perl/5.25.4/Test/Pod/Coverage.pm line 133. > # LPDS::RendererModel: couldn't find pod > > # Failed test 'Pod coverage on LPDS::RendererAxis' > # at /opt/perl-5.25.4/lib/site_perl/5.25.4/Test/Pod/Coverage.pm line 133. > # LPDS::RendererAxis: couldn't find pod > > # Failed test 'Pod coverage on LPDS::Renderer' > # at /opt/perl-5.25.4/lib/site_perl/5.25.4/Test/Pod/Coverage.pm line 133. > # LPDS::Renderer: couldn't find pod > # Looks like you failed 4 tests of 5. > t/pod-coverage.t .. > Dubious, test returned 4 (wstat 1024, 0x400) > Failed 4/5 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};
  Thu Sep 01 02:12:36 2016 The RT System itself - Status changed from 'new' to 'open'