By now your module should have generated test reports for Perl 5.18.0, as well as for several later releases of Perl 5.17. If you visit cpantesters.org and find that your distribution has generated at least one "PASS" under 5.18, that's a reasonably good indication that your test suite hasn't detected a problem related to 5.18 in particular.
In some cases it's the test suites themselves that are at fault; I've seen tests that expect hash order to remain consistent from one inspection to the next, and that's the sort of thing that shouldn't be relied upon. In other cases, it's the module's primary code that has a problem. *hopefully* such problems are detected by your existing test suite. But you know your code base better than anyone (presumably)... If you think you might have a problem that your tests aren't uncovering, further investigation is probably worthwhile. But a good first step is just to assure that you've got a PASS on a 5.18.0 platform. Certainly if you were generating PASS under 5.16, and now have 100% FAIL under 5.18, where nothing else has changed in the code, you've found something worth digging into right away. :) Dave On Thu, May 23, 2013 at 12:40 AM, Shmuel Fomberg <shmuelfomb...@gmail.com> wrote: > Hi Gabor. > > On Thu, May 23, 2013 at 3:06 PM, Gabor Szabo wrote: > >> >> with the release of 5.18 some modules might stop working 100%. >> Please take a look at the call of David Oswald and, please update your >> module to make it work on 5.18 as well: > > > So we can sit back and relax while the automated CPAN testers are doing > their thing and will send us failure reports? > > Shmuel. > -- David Oswald daosw...@gmail.com
