Skip Menu |

This queue is for tickets about the Martian CPAN distribution.

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

History Show all quoted text
  Fri Nov 24 15:32:38 2017 SREZIC [...] cpan.org - Ticket created
Subject: t/pod-coverage.t may fail
The pod coverage test fails on some of my smokers: ... # Failed test 'Pod coverage on Martian::Server' # at /usr/perl5.26.1t/lib/site_perl/5.26.1/Test/Pod/Coverage.pm line 133. # Martian::Server: requiring 'Martian::Server' failed # Failed test 'Pod coverage on Plack::Handler::Martian' # at /usr/perl5.26.1t/lib/site_perl/5.26.1/Test/Pod/Coverage.pm line 133. # Plack::Handler::Martian: requiring 'Plack::Handler::Martian' failed # Looks like you failed 2 tests of 3. t/pod-coverage.t ....... Dubious, test returned 2 (wstat 512, 0x200) Failed 2/3 subtests ... Probably this happens were optional prereqs are not met --- Test::Pod::Coverage does not seem to skip tests properly in this case.
  Sun Nov 26 02:36:50 2017 ether [...] cpan.org - Correspondence added
On 2017-11-24 12:32:38, SREZIC wrote: Show quoted text
> The pod coverage test fails on some of my smokers: > > ... > # Failed test 'Pod coverage on Martian::Server' > # at /usr/perl5.26.1t/lib/site_perl/5.26.1/Test/Pod/Coverage.pm line > 133. > # Martian::Server: requiring 'Martian::Server' failed > > # Failed test 'Pod coverage on Plack::Handler::Martian' > # at /usr/perl5.26.1t/lib/site_perl/5.26.1/Test/Pod/Coverage.pm line > 133. > # Plack::Handler::Martian: requiring 'Plack::Handler::Martian' failed > # Looks like you failed 2 tests of 3. > t/pod-coverage.t ....... > Dubious, test returned 2 (wstat 512, 0x200) > Failed 2/3 subtests > ... > > Probably this happens were optional prereqs are not met --- > Test::Pod::Coverage does not seem to skip tests properly in this case.
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};
  Sun Nov 26 02:36:50 2017 The RT System itself - Status changed from 'new' to 'open'