Skip Menu |

This queue is for tickets about the Config-Cascade CPAN distribution.

Report information
The Basics
Id: 129154
Status: open
Priority: 0/
Queue: Config-Cascade
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
  Sat Apr 13 04:26:47 2019 SREZIC [...] cpan.org - Ticket created
Subject: t/pod-coverage.t fails
See subject. Excerpt of test log: ... # Failed test 'Pod coverage on Config::Cascade' # at /usr/perl5.28.2-RC1p/lib/site_perl/5.28.2/Test/Pod/Coverage.pm line 133. # Coverage for Config::Cascade is 16.7%, with 5 naked subroutines: # constructValidation # loadConfigFile # loadDefaultValidation # parseCommandLine # validateConfig # Looks like you failed 1 test of 1. t/pod-coverage.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests ...
  Sat Apr 13 21:14:23 2019 ether [...] cpan.org - Correspondence added
On 2019-04-13 01:26:47, SREZIC wrote: Show quoted text
> See subject. Excerpt of test log: > > ... > # Failed test 'Pod coverage on Config::Cascade'
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};
  Sat Apr 13 21:14:24 2019 The RT System itself - Status changed from 'new' to 'open'