Err, thanks. But there's almost no information about the problem.
I'm CC'ing this to [email protected] to ask if anyone knows
why it said "Detailed output could not be captured with test.pl and make."
This is a limitation in the current version of CPAN::Reporter.
My understanding is that ExtUtils::MakeMaker creates a Makefile that executes test.pl directly and uses the result code to determine success or failure. It does not pass test.pl to Test::Harness, so CPAN::Reporter can't reliably parse for success. (And it gets run right after all tests from t/*.t).
As a result, I can't tee the output of test.pl as that obscures the exit code. I can't just capture without teeing or there would be no visible output, no way to respond to prompts and no way to know if the test has hung. So when test.pl exists and "make test" is the command from CPAN.pm, CPAN::Reporter punts. Interestingly, Module::Build always passes test.pl to Test::Harness.so that can be teed.
I'll grant it needs a better diagnostic.
Andreas has suggested running "make test" again on failure, the second time with output captured. I haven't gotten around to implementing it -- and I'm not sure if I want to do so without adding a prompt and having an option to turn it off. In part, I was waiting to see if it would be even be a problem -- I don't think many distros still use test.pl.
Well, DBI is important enough for it to be a problem.
test.pl is flagged as being "mostly an empty shell". Can it be removed entirely or moved to the examples directory? Or do I need to prioritize getting some sort of output capture even in the case of test.pl? In this case, since t/*.t is run as well, the Test::Harness "All tests successful" line would get picked up and the the results of test.pl would be ignored.
Regards,
David Golden
