On Tue, 21 Dec 2004, _brian_d_foy wrote:
It's not that the testers ignore it. they don't even look at it.
Most of CPAN Testers is automated, so it just happens and the responsible person doesn't monitor it. Add to that various versions of CPANPLUS which have various bugs, and you get a lot of bad reports.
I had a similar rant about cpan-testers on module-authors in September. It seems like the automated reporting is so easy, the testers don't stop to determine whether *they* are the source of the problem. (I thought it was fully automated by a testing farm somewhere, based on the brain-dead submissions I was getting.) Perhaps we need a "Testing HOWTO" that the testers have to read before we let them submit reports.
The frustrating thing is that the failure reports on CPAN indicate that a module is buggy when it's not. As a result, modules that depend on external modules, libraries, or programs tend to get unfairly "graded". It hurts the reputation of the author. (In my case, such as it is. :)
David
_____________________________________________________________________ David Coppit [EMAIL PROTECTED] The College of William and Mary http://coppit.org/
"Government big enough to supply everything you need is big enough to take everything you have ... The course of history shows that as a government grows, liberty decreases." -- Thomas Jefferson
