Skip Menu |
 

This queue is for tickets about the Metabrik CPAN distribution.

Report information
The Basics
Id: 118279
Status: open
Priority: 0/
Queue: Metabrik

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

Bug Information
Severity: (no value)
Broken in:
  • 1.24
  • 1.26
Fixed in: (no value)



Subject: pod coverage test fails (1.24)
Download (untitled) / with headers
text/plain 360b
My smoker machines report the following failure: # Failed test 'Pod coverage on Metabrik::Core::Shell' # at t/02-pod-coverage.t line 11. # Coverage for Metabrik::Core::Shell is 95.0%, with 2 naked subroutines: # cmd # full_pwd # Looks like you failed 1 test of 5. t/02-pod-coverage.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/5 subtests
On 2016-10-06 10:37:27, SREZIC wrote: Show quoted text
> My smoker machines report the following failure: > > # Failed test 'Pod coverage on Metabrik::Core::Shell' > # at t/02-pod-coverage.t line 11. > # Coverage for Metabrik::Core::Shell is 95.0%, with 2 naked subroutines: > # cmd > # full_pwd > # Looks like you failed 1 test of 5. > t/02-pod-coverage.t .. > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/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};


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.