cpan testers is /dev/null?

jjore on 2007-09-25T15:35:21

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 cpantesters.perl.org either.


Works for me

brian_d_foy on 2007-09-25T16:08:55

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.

Re:Works for me

jjore on 2007-09-25T16:37:45

I don't do RSS. I've never met an RSS client I liked.

Re:Works for me

brian_d_foy on 2007-09-25T16:47:37

I don't really like RSS readers either, but I do what I can to get the information I need.

Re:Works for me

jjore on 2007-09-25T17:03:39

I figure I don't need the information if its going to come in such inconvenient packages.

Re:Works for me

bart on 2007-10-10T05:58:51

Maybe you cold take a look at NetVibes, which is like an RSS reader in a customizable web page — using Javascript. Web 2.0 at its best.

*It* is decentralized

dagolden on 2007-09-25T18:43:25

FYI, there is no centralized "it" to be /dev/null. Individual testers may configure their CPAN Tester client to CC authors or not.

-- David

Your email? Or something else?

dagolden on 2007-09-25T16:26:39

My first thought is that there could be something wrong with emailing to your PAUSE ID at cpan.org. 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 only be on the mailing list and website -- you wouldn't get them directly.

There's a new crop of smokers that are pretty aggressive about smoking any new releases within a day or so. Some of them are bleadperl, too. So you might want to just kick out a new release and that will trigger a bunch of smoking.

Note -- I tried it on my bleadperl with CPAN::Reporter and it was a pass. So keep an eye out and see if it shows up on CPAN Testers.

-- David

How many smokers email reports?

mr_bean on 2007-09-26T00:20:37

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!

Speaking for CPANPLUS

BinGOs on 2007-09-26T06:27:36

CPANPLUS pulls the .yml file from cpantesters.perl.org 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.