Johan Vromans wrote: > We all love the CPAN testers and the results publised at > http://testers.cpan.org.
Except when failure reports reflect problems in a particular tester's environment, and not problems with the modules being tested. (But that goes without saying, right?) > But recently I suddenly saw a big load of failures in one of my > packages. All these failures were for 5.11.0. > > Now, 5.11.0 is a development version, and a moving target. A test > failure with blead reveals often more about blead than about the > tested package. I routinely report tests against blead. I don't see failures often, and when I do, they usually reflect some new change in Perl that requires a subsequent change in the module. When I encounter such cases, I try to figure out a patch and then report it as bug (along with the patch) against the affected module. > So, on one hand, it is a good thing that packages are being tested with > blead versions. On the other hand, when users want to find out if a > package is usable they're only interested in released versions of > perl. > > What are your ideas about this? Should blead test results be separated > from the other results? I agree they should be segregated. However, they should also be reported to the module's maintainers so they can fix things appropriately.
