Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Journal of jjore (6662)

Tuesday September 25, 2007
10:35 AM

cpan testers is /dev/null?

[ #34542 ]

By chance I looked at the tester reports for overload::eval and discovered that its never worked for anyone else. I never got a note about it failing or anything.

How's an author supposed to get notified that stuff is broken? I thought the new cpan test reporting stuff was supposed to make sure I'd get cc-ed on failures. Apparently it doesn't. There's nothing that looks helpful on either.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • I still get lots of fail reports, so it's not /dev/null. :)

    I also look at the RSS feed for my PAUSE ID too, though.
  • My first thought is that there could be something wrong with emailing to your PAUSE ID at Or something filtering emails on their way to you. But the overall number of reports on cpan testers is pretty low.

    With the addition of the 5.9 dependency, I'm surprised there aren't any N/A results -- which would be the correct report to see on CPAN Testers for older Perls. Note that N/A reports are now not sent to authors by CPAN::Reporter, and possibly not by CPANPLUS/YACSmoke either. So those should

  • I only get FAIL reports from David Cantrell, so I was
    surprised to see half of the reports on cpantesters for me
    were failures.

    That said, I have ambivalent feelings about getting more
    FAIL reports in my mailbox.

    But, seriously, smokers, Good Job!
  • CPANPLUS pulls the .yml file from []to determine if a FAIL has already been reported or not. If a FAIL already has, it skips sending the cc'd email to the module author.