Skip Menu |

This queue is for tickets about the Config-NameValue CPAN distribution.

Report information
The Basics
Id: 74228
Status: resolved
Worked: 3 hours (180 min)
Priority: 0/
Queue: Config-NameValue

People
Owner: AYOUNG [...] cpan.org
Requestors: ANDK [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 1.01
Fixed in: 1.03



Subject: Fails with 5.10.0
As per subject Sample fail report http://www.cpantesters.org/cpan/report/19216817 This is happening from time to time with nowarnings tests. The warnings comes from another module, not your own code. HTH,
I have been unable to reproduce this, though I don't have access to 5.10.0--I realize I could find it somewhere and install it with perlbrew. As far as I can tell, 5.10.0 is deprecated and should be replaced with 5.10.1. All of the fail reports on cpantester are for 5.10.0 as well. Unless this is a serious issue or you have a convincing argument otherwise, I'll close this ticket as rejected in a few days.
I'm not trying to convince you to do something, there are just a few other options for your next release. By closing the ticket the red cpantesters reports will come again after your next release. How about making the nowarnings test a skipall for the case that perl eq 5.10.0 and File::Slurp eq 9999.19. Or using a technique described on http://wiki.cpantesters.org/wiki/CPANAuthorNotes: either require 5.10.1 directly or only then when the running perl is exactly 5.10.0. With these simple measures you can make sure you only get fail reports from cpantesters that are actually interesting. You choose:)
On Thu Jan 26 00:59:45 2012, ANDK wrote: Show quoted text
> With these simple measures you can make sure you only get fail reports > from cpantesters that are actually interesting.
Thank you. I was not aware of either of these options. Show quoted text
> You choose:)
:]
On Thu Jan 26 00:59:45 2012, ANDK wrote: Show quoted text
> With these simple measures you can make sure you only get fail
Done in 1.03. I'll wait for results from CpanTesters before closing this ticket. Thanks for the pointers.