Bug #91457 for Locale-Codes: pod coverage failing

Mon Dec 16 21:56:17 2013 xenoterracide [...] gmail.com - Ticket created

Subject:	pod coverage failing
Date:	Mon, 16 Dec 2013 20:56:07 -0600
To:	bugs-locale-codes [...] rt.cpan.org
From:	Caleb Cushing <xenoterracide [...] gmail.com>

I suspect it's just a specific version of a library causing this, but it might be more ideal to make pod coverage tests AUTHOR_TESTING or RELEASE_TESTING only https://travis-ci.org/xenoterracide/MooseX-Types-Locale-Currency/jobs/15562954 Failed test 'Pod coverage on Locale::Codes::LangVar_Retired' # at /home/travis/perl5/perlbrew/perls/5.14/lib/site_perl/5.14.4/Test/Pod/Coverage.pm line 126. # Locale::Codes::LangVar_Retired: couldn't find pod # Failed test 'Pod coverage on Locale::Codes::LangExt_Retired' # at /home/travis/perl5/perlbrew/perls/5.14/lib/site_perl/5.14.4/Test/Pod/Coverage.pm line 126. # Locale::Codes::LangExt_Retired: couldn't find pod # Failed test 'Pod coverage on Locale::Codes::Currency_Codes' # at /home/travis/perl5/perlbrew/perls/5.14/lib/site_perl/5.14.4/Test/Pod/Coverage.pm line 126. # Locale::Codes::Currency_Codes: couldn't find pod # Failed test 'Pod coverage on Locale::Codes::Country_Codes' # at /home/travis/perl5/perlbrew/perls/5.14/lib/site_perl/5.14.4/Test/Pod/Coverage.pm line 126. # Locale::Codes::Country_Codes: couldn't find pod # Failed test 'Pod coverage on Locale::Codes::LangExt_Codes' # at /home/travis/perl5/perlbrew/perls/5.14/lib/site_perl/5.14.4/Test/Pod/Coverage.pm line 126. # Locale::Codes::LangExt_Codes: couldn't find pod # Failed test 'Pod coverage on Locale::Codes::LangVar_Codes' # at /home/travis/perl5/perlbrew/perls/5.14/lib/site_perl/5.14.4/Test/Pod/Coverage.pm line 126. # Locale::Codes::LangVar_Codes: couldn't find pod # Failed test 'Pod coverage on Locale::Codes::Language_Retired' # at /home/travis/perl5/perlbrew/perls/5.14/lib/site_perl/5.14.4/Test/Pod/Coverage.pm line 126. # Locale::Codes::Language_Retired: couldn't find pod # Failed test 'Pod coverage on Locale::Codes::Currency_Retired' # at /home/travis/perl5/perlbrew/perls/5.14/lib/site_perl/5.14.4/Test/Pod/Coverage.pm line 126. # Locale::Codes::Currency_Retired: couldn't find pod # Failed test 'Pod coverage on Locale::Codes::Script_Codes' # at /home/travis/perl5/perlbrew/perls/5.14/lib/site_perl/5.14.4/Test/Pod/Coverage.pm line 126. # Locale::Codes::Script_Codes: couldn't find pod # Failed test 'Pod coverage on Locale::Codes::Script_Retired' # at /home/travis/perl5/perlbrew/perls/5.14/lib/site_perl/5.14.4/Test/Pod/Coverage.pm line 126. # Locale::Codes::Script_Retired: couldn't find pod # Failed test 'Pod coverage on Locale::Codes::Language_Codes' # at /home/travis/perl5/perlbrew/perls/5.14/lib/site_perl/5.14.4/Test/Pod/Coverage.pm line 126. # Locale::Codes::Language_Codes: couldn't find pod # Failed test 'Pod coverage on Locale::Codes::Country_Retired' # at /home/travis/perl5/perlbrew/perls/5.14/lib/site_perl/5.14.4/Test/Pod/Coverage.pm line 126. # Locale::Codes::Country_Retired: couldn't find pod # Failed test 'Pod coverage on Locale::Codes::LangFam_Codes' # at /home/travis/perl5/perlbrew/perls/5.14/lib/site_perl/5.14.4/Test/Pod/Coverage.pm line 126. # Locale::Codes::LangFam_Codes: couldn't find pod # Looks like you failed 13 tests of 27. [02:49:31] t/pod_coverage.t ........... Dubious, test returned 13 (wstat 3328, 0xd00) Failed 13/27 subtests [02:49:31] t/pod.t .................... ok 1179 ms [02:49:31] Test Summary Report ------------------- t/pod_coverage.t (Wstat: 3328 Tests: 27 Failed: 13) Failed tests: 6-9, 11, 14, 17, 19, 21, 23, 25-27 Non-zero exit status: 13 -- Caleb Cushing http://xenoterracide.com Calendar: https://www.google.com/calendar/embed?src=xenoterracide%40gmail.com&ctz=America/Chicago

Tue Dec 17 08:06:52 2013 sbeck [...] cpan.org - Correspondence added

This was already reported, and it will be fixed in the next release due out March 1. I thought I had fixed this a while ago, but I don't pay much attention to the pod tests typically, so this slipped by me.

Tue Dec 17 08:06:53 2013 The RT System itself - Status changed from 'new' to 'open'

Tue Dec 17 08:06:53 2013 sbeck [...] cpan.org - Status changed from 'open' to 'resolved'

Wed Dec 18 09:34:51 2013 xenoterracide [...] gmail.com - Correspondence added

Subject:	Re: [rt.cpan.org #91457] pod coverage failing
Date:	Wed, 18 Dec 2013 08:34:40 -0600
To:	bug-Locale-Codes [...] rt.cpan.org
From:	Caleb Cushing <xenoterracide [...] gmail.com>

On Tue, Dec 17, 2013 at 7:06 AM, Sullivan Beck via RT < bug-Locale-Codes@rt.cpan.org> wrote: Show quoted text

> This was already reported, and it will be fixed in the next release due > out March 1. > > I thought I had fixed this a while ago, but I don't pay much attention to > the pod tests typically, so this slipped by me. >

why wait another 4 months to fix a test? I can understand 4 months for a feature release... but not a test... -- Caleb Cushing http://xenoterracide.com Calendar: https://www.google.com/calendar/embed?src=xenoterracide%40gmail.com&ctz=America/Chicago

Wed Dec 18 09:52:07 2013 sbeck [...] cpan.org - Correspondence added

Several reasons: 1) Time. I'm leaving for break and won't have time to get out a release until January 2-3 at the earliest. (And by the way, the releases are every 3 months, not every 4 months). 2) This is a core module which means that a release isn't just a matter of putting a new version on CPAN. If that's all it were, I'd do it for sure. But with a core module, I have to do additional work to prep it for the core, submit a patch to the maintainers, etc. Because it puts extra work on me, and even more importantly ON THEM, I'm hesitant to do a new release that doesn't fix a problem for the module as it appears in core. Since the core modules always excludes pod tests, this problem has absolutely no effect on core. 3) It's not a bug in the module. It's a pod test. Admittedly, that is still a problem that needs to be corrected, but the question is urgency. 4) Of the module testers, there are 13 failures and 414 successes. More than I'd like (I like to see 0 failures), but given all the factors, I'm ranking this as 'serious nuisance' instead of 'urgent fix needed'. Anyway, I'll check on it's status again when I get back from break, and reevaluated then, and I may be able to put out a release the first week of January.

Wed Dec 18 10:40:12 2013 xenoterracide [...] gmail.com - Correspondence added

Subject:	Re: [rt.cpan.org #91457] pod coverage failing
Date:	Wed, 18 Dec 2013 09:39:53 -0600
To:	bug-Locale-Codes [...] rt.cpan.org
From:	Caleb Cushing <xenoterracide [...] gmail.com>

On Wed, Dec 18, 2013 at 8:52 AM, Sullivan Beck via RT < bug-Locale-Codes@rt.cpan.org> wrote: Show quoted text

> > 2) This is a core module which means that a release isn't just a matter > of putting a new version on CPAN. If that's all it were, I'd do it for > sure. But with a core module, I have to do additional work to prep it for > the core, submit a patch to the maintainers, etc. Because it puts extra > work on me, and even more importantly ON THEM, I'm hesitant to do a new > release that doesn't fix a problem for the module as it appears in core. > Since the core modules always excludes pod tests, this problem has > absolutely no effect on core. >

so you have to submit a patch to core for a dual life module even if it doesn't affect the core? (pod tests) would seem like people could safely ignore it.... Show quoted text

> 3) It's not a bug in the module. It's a pod test. Admittedly, that is > still a problem that needs to be corrected, but the question is urgency. > > 4) Of the module testers, there are 13 failures and 414 successes. More > than I'd like (I like to see 0 failures), but given all the factors, I'm > ranking this as 'serious nuisance' instead of 'urgent fix needed'. >

it's 100% of the time in a new environment on a version of perl older than... I think 5.16? Any version that doesn't ship with version 3, for me. cpantesters mix up module versions more than a clean CI environment, meaning some of them have version 3 on an older Perl. Which is fundamentally why I'm pushing a little more, the choices for new environments on older perls (including TravisCI) is to skip tests for this module (obviously that's probably still serious nuisance). Show quoted text

> > Anyway, I'll check on it's status again when I get back from break, and > reevaluated then, and I may be able to put out a release the first week of > January. >

Alright, I guess that'll have to be good enough for me. Thanks for explaining, I just didn't understand the motivation behind it. -- Caleb Cushing http://xenoterracide.com Calendar: https://www.google.com/calendar/embed?src=xenoterracide%40gmail.com&ctz=America/Chicago

Tue Jan 28 07:43:49 2014 sbeck [...] cpan.org - Correspondence added

I released a new version yesterday to correct a different issue, but it also addresses this.