Hi David,
I think you have a couple misconceptions about cpan-testers. It's not some organization with an office and some testing machines, it's just regular people out there who have set up robots to test all the CPAN releases they see (or that interest them). There are also lots of people who manually send reports of success or failure of modules as they test & install them. The only centralization is the testers.cpan.org web site & mailing list, which serve to consolidate the test reports in one place.
So no, module authors don't typically have access to the test machines. ;-)
Also, my hunch is that yes, Module::Install may be part of the culprit here. But without us seeing any of the output they sent you, it's, um, hard to fix a bug if you can't reproduce it.
-Ken
On Sep 17, 2004, at 6:46 AM, David Coppit wrote:
Can someone please tell me how to convince cpan-tester's automated testing
to:
- Not test unless required modules are installed. (Of *course* it fails if
you don't have a required module installed.)
- Send me the output of "make test TEST_VERBOSE=1" instead of the useless
general testing report. (Test X failed, but you'll have to guess why!)
- Make sure they're using the right lib version (5.8.5) for their perl
version (5.6.1)
I recently switched to Module::Install, if that makes a difference in how
to tell cpan-testers about required modules.
Also, do module authors have access to the test machines? It's hard to fix
a bug if you can't reproduce it.
Thanks, David
