On Thu, 20 Dec 2007, David Golden wrote:
On Dec 20, 2007 1:19 PM, Dave Rolsky <[EMAIL PROTECTED]> wrote:
It's generally
pretty rare that the failure report includes enough information for me to
do anything about it, so without an engaged party on the other end, it
really is just noise.
With CPAN::Reporter, I've been trying to add additional context
(within reason) to assist with problem diagnosis. What kind of
information would improve the reports? (Not to say that this obviates
the need for a responsive tester, but every little bit helps.)
Getting the full TAP as Michael P mentioned would be good.
However, usually I end up needing to investigate aspects of the testers
platform, often by having them run snippets of Perl code from the shell,
or asking them to try a patch. There's not much you can do to automate
that.
As chromatic mentioned, failures often happen on platforms to which I as a
module author don't have ready access, so I need some assistance from the
user of that platform.
-dave
/*===================================================
VegGuide.Org www.BookIRead.com
Your guide to all that's veg. My book blog
===================================================*/
