Skip Menu |

This queue is for tickets about the Timeout-Queue CPAN distribution.

Report information
The Basics
Id: 117825
Status: open
Priority: 0/
Queue: Timeout-Queue

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

Bug Information
Severity: (no value)
Broken in: 1.02
Fixed in: (no value)



Subject: perlcritic test may fail
On some of my smoker systems tests fail: # Failed test 'Test::Perl::Critic for "blib/lib/Timeout/Queue.pm"' # at /usr/perl5.24.1-RC3p/lib/site_perl/5.24.1/Test/Perl/Critic.pm line 104. # # Perlsecret risk. Venus at line 100, column 9. Perlsecret detected: %s. (Severity: 5) # Perlsecret risk. Venus at line 215, column 24. Perlsecret detected: %s. (Severity: 5) # Perlsecret risk. Venus at line 241, column 9. Perlsecret detected: %s. (Severity: 5) t/critic.t ........... Dubious, test returned 1 (wstat 256, 0x100) See also http://analysis.cpantesters.org/solved?distv=Timeout-Queue-1.02#qr%3A%28Failed%20test\s%2B\S%2B.*%29 for an overview.
On 2016-09-13 13:12:48, SREZIC wrote: Show quoted text
> On some of my smoker systems tests fail: > > # Failed test 'Test::Perl::Critic for "blib/lib/Timeout/Queue.pm"' > # at /usr/perl5.24.1-RC3p/lib/site_perl/5.24.1/Test/Perl/Critic.pm > line 104. > # > # Perlsecret risk. Venus at line 100, column 9. Perlsecret > detected: %s. (Severity: 5) > # Perlsecret risk. Venus at line 215, column 24. Perlsecret > detected: %s. (Severity: 5) > # Perlsecret risk. Venus at line 241, column 9. Perlsecret > detected: %s. (Severity: 5) > t/critic.t ........... > Dubious, test returned 1 (wstat 256, 0x100) > > > See also http://analysis.cpantesters.org/solved?distv=Timeout-Queue- > 1.02#qr%3A%28Failed%20test\s%2B\S%2B.*%29 for an overview.
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};