On Tuesday 02 September 2008 16:53:31 Barbie wrote: > > http://www.nntp.perl.org/group/perl.cpan.testers/2008/08/msg2029059.html > > Please note that I don't care *why* this occurred.
> But you're willing to shoot down cpan-testers just because they're the > messenger! Thanks. I believe that someone interested in reporting test results for CPAN distributions should use working tools which do not spew useless and incorrect information into my inbox and on search.cpan.org's distribution pages. I didn't ask for anyone to set up automatic tests for my distributions. I'm happy to get useful information out of them -- but when there's an automated process seemingly spiraling out of control with a configuration that couldn't possibly tell the difference between a pass and a fail, you'd better believe that there's something wrong -- and I'm not sorry that I'm not thankful that someone bothered to set up a useless answers process that produces irrelevant and useless and confusing information. > The problem is CPANPLUS trying to be backward compatible. I suggest you > take this up on the cpanplus mailing list. I don't care where the problem is. Why is this even a CPAN Testers report? A CPAN client that cannot install distributions correctly is not an interesting target for test results. > This is exactly the same attitude that forced me to quit being a tester > a few years ago. For some reason authors decide to ignore the fact that > CPANPLUS has made a decision they don't like and sees cpan-testers as an > easy target instead. Like I said, I don't care where the problem is. I don't use CPANPLUS. I'm happy with people complaining to CPANPLUS if that's where the bug is. I'm not happy with getting FAIL reports from CPAN Testers clients that can't possibly produce PASS reports. This is not my bug. This is not my responsibility to fix. This is not my problem. Notifying me accomplishes precisely nothing positive. Putting a little black mark on search.cpan.org for my distributions misleads my potential users into believing that I don't write good code. Short of opting out of CPAN Testers entirely (and I'm not looking forward to updating and uploading new versions of 30+ distributions to do so) and asking CPAN Testers to fix the brokenness over the period of a couple of years, exactly what do you recommend I do? The only reason it affects me is because some CPAN Tester somewhere has a buggy toolchain that I don't control and I didn't install. It is not my bug. It is not my responsibility to fix. Now imagine you're not me, you don't have 30+ distributions on the CPAN, you haven't written multiple books on Perl, you didn't help develop Perl Monks, you haven't spoken at multiple Perl conferences, you don't have core patches in several versions of Perl, and you don't know just about everyone involved in all of these projects. What are you supposed to do about it? Now multiply that by the other 6000 CPAN developers in similar situations. *THAT* is my problem. If that's worthy of sarcastic dismissal, well, sarcastic dismissal me harder. I can't see how it helps anything though. -- c
