Skip Menu |

This queue is for tickets about the Net-Amazon-ATS CPAN distribution.

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

History Show all quoted text
  Thu Feb 13 16:53:51 2020 SREZIC [...] cpan.org - Ticket created
Subject: t/pod_coverage.t fails
The test suite fails if Test::Pod::Coverage is installed: ... # Failed test 'Pod coverage on Net::Amazon::ATS' # at /usr/perl5.28.1Dp/lib/site_perl/5.28.1/Test/Pod/Coverage.pm line 133. # Coverage for Net::Amazon::ATS is 50.0%, with 1 naked subroutine: # topsites # Looks like you failed 1 test of 1. t/pod_coverage.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests ...
  Thu Feb 13 17:02:17 2020 SREZIC [...] cpan.org - Correspondence added
On 2020-02-13 16:53:51, SREZIC wrote: Show quoted text
> The test suite fails if Test::Pod::Coverage is installed: > > ... > # Failed test 'Pod coverage on Net::Amazon::ATS' > # at /usr/perl5.28.1Dp/lib/site_perl/5.28.1/Test/Pod/Coverage.pm line 133. > # Coverage for Net::Amazon::ATS is 50.0%, with 1 naked subroutine: > # topsites > # Looks like you failed 1 test of 1. > t/pod_coverage.t .. > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/1 subtests > ...
Sometimes the test fails in a different way, suggesting a module compilation problem: ... # Failed test 'Pod coverage on Net::Amazon::ATS' # at /opt/perl-5.31.7/lib/site_perl/5.31.7/Test/Pod/Coverage.pm line 133. # Net::Amazon::ATS: requiring 'Net::Amazon::ATS' failed # Looks like you failed 1 test of 1. t/pod_coverage.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests ...
  Wed Feb 19 23:59:34 2020 ether [...] cpan.org - Correspondence added
On 2020-02-13 13:53:51, SREZIC wrote: Show quoted text
> The test suite fails if Test::Pod::Coverage is installed:
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};
  Wed Feb 19 23:59:34 2020 The RT System itself - Status changed from 'new' to 'open'