All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Please Log In to Continue

One thing that'd be immensely helpful to me is an RSS feed containing just FAILs. As it stands I regularly get 20-80 reports in my RSS reader, most of which are not interesting (PASS, NA, etc). I just want the failure reports!

Yes, only getting failure reports for actual test failures would be great. I can live with failures because a broken toolchain didn't install the deps properly. But getting fail reports because the path was too long because they're using Red Hat, or whatever, is just damn annoying.

Anyway, as an author who does have mostly high quality distros (I think), there are still cases where CPAN testers is really useful.

Recently I shepherded the new Class::MOP and Moose releases. These included a lot of big changes, so we did dev releases specifically to get CPAN tester reports back. These reports were very helpful and we cleaned up quite a few bugs that way. This specific use case was great, and not something I'd really done before.

I'd like to join jplindstrom in thanking all CPANTesters (both frontend and backend) for the good service.

One thing that surprised me a little was this "message avalanche" effect, which I thought was an already-dealt-with problem. In particular, I notice that I only get one single FAIL message for each module that I upload to PAUSE that has problems, even when there are more of them. Am I totally misunderstanding this point in your post, or have I been gifted by some obscure bug^Wfeature?

Some CPAN Testers have configured their machines not to CC authors at all or not to CC authors for certain grades or PL/make/test phases. I suspect your experience is serendipity, not fundamental design.