Skip Menu |

This queue is for tickets about the POE-Filter-SSL CPAN distribution.

Report information
The Basics
Id: 122573
Status: resolved
Priority: 0/
Queue: POE-Filter-SSL
People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in:
  • 0.33
  • 0.34
  • 0.35
Fixed in: (no value)

History Show all quoted text
  Sun Jul 23 09:06:05 2017 SREZIC [...] cpan.org - Ticket created
Subject: More pod coverage problems (0.33)
t/pod-coverage.t is still failing: # Failed test 'Pod coverage on POE::Filter::SSL' # at /usr/perl5.16.3t/lib/site_perl/5.16.3/Test/Pod/Coverage.pm line 133. # Coverage for POE::Filter::SSL is 86.2%, with 4 naked subroutines: # CTX_add_client_CA # PEMdataToEVP_PKEY # PEMdataToX509 # dataToBio # Looks like you failed 1 test of 1. t/pod-coverage.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests
  Wed Jul 26 14:53:34 2017 ether [...] cpan.org - Correspondence added
On 2017-07-23 06:06:05, SREZIC wrote: Show quoted text
> t/pod-coverage.t is still failing: > > # Failed test 'Pod coverage on POE::Filter::SSL' > # at /usr/perl5.16.3t/lib/site_perl/5.16.3/Test/Pod/Coverage.pm line 133. > # Coverage for POE::Filter::SSL is 86.2%, with 4 naked subroutines: > # CTX_add_client_CA > # PEMdataToEVP_PKEY > # PEMdataToX509 > # dataToBio > # Looks like you failed 1 test of 1. > t/pod-coverage.t .. > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/1 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};
  Wed Jul 26 14:53:35 2017 The RT System itself - Status changed from 'new' to 'open'
  Mon Aug 21 17:10:42 2017 SREZIC [...] cpan.org - Subject changed from 'More pod coverage problems (0.33)' to 'More pod coverage problems (0.33+0.34)'
  Mon Aug 21 17:10:42 2017 SREZIC [...] cpan.org - Broken in 0.33 added
  Mon Aug 21 18:25:32 2017 PRIVI [...] cpan.org - Correspondence added
Show quoted text
> More pod coverage problems (0.33+0.34)
oh, sorry, I will fix it in 0.35 within the next days... Thank you for reporting!
  Mon Oct 30 21:15:23 2017 PRIVI [...] cpan.org - Correspondence added
Resolved in 0.35
  Mon Oct 30 21:15:24 2017 PRIVI [...] cpan.org - Status changed from 'open' to 'resolved'
  Tue Oct 31 03:57:33 2017 SREZIC [...] cpan.org - Correspondence added
On 2017-10-30 21:15:23, PRIVI wrote: Show quoted text
> Resolved in 0.35
Reopened --- I still see pod coverage errors in 0.35: # Failed test 'Pod coverage on POE::Filter::SSL' # at /usr/perl5.16.3t/lib/site_perl/5.16.3/Test/Pod/Coverage.pm line 133. # Coverage for POE::Filter::SSL is 86.2%, with 4 naked subroutines: # CTX_add_client_CA # PEMdataToEVP_PKEY # PEMdataToX509 # dataToBio # Looks like you failed 1 test of 1. t/pod-coverage.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests
  Tue Oct 31 03:57:53 2017 SREZIC [...] cpan.org - Broken in 0.34 added
  Tue Oct 31 03:57:53 2017 SREZIC [...] cpan.org - Broken in 0.35 added
  Tue Oct 31 07:23:02 2017 PRIVI [...] cpan.org - Correspondence added
On Tue Oct 31 03:57:33 2017, SREZIC wrote: Show quoted text
> On 2017-10-30 21:15:23, PRIVI wrote:
> > Resolved in 0.35
> > Reopened --- I still see pod coverage errors in 0.35:
Now it should be fixed realy. :-) Thank you for your patience...