|
Posted by Mumia W. on August 8, 2007, 10:17 pm
Please log in for more thread options
On 08/08/2007 06:37 PM, Jens Thoms Toerring wrote:
> Hi,
>
> I hope this isn't too stupid a question, but I haven't found
> answers by looking up FAQs and googling. I have uploaded a module
> to CPAN and now the test results from CPAN Tester are coming in.
> There's one failure I don't understand yet but which taught me
> to use more verbose output for failed tests (in the hope that they
> will show up in the reports). What I couldn't figure out is what
> results marked as "NA" actually mean. My module depends on a few
> other modules (nothing exotic but, of course, they could be not
> installed on the testers machine) and I do some tests in the
> Makefile.PL to check if a C compiler can be used and if a certain
> system call exists on the machine - failures should result in an
> error message. Unfortunately, nothing shows up in the reports for
> the "NA" cases, only some information about the test machine.
> Thus I am uncertain what could have led to these cases and how
> to deal with them (and if there's a way to write the Makefile.PL
> so that more information is returned).
>
> Another point: I guess the testers are quite busy and could very
> well understand if they are not too keen to also get flooded
> with questions from authors of modules they were kind enough to
> test. Is there a good way to get at more information without
> bothering the testers too much?
>
> Regards, Jens
Probably you've required modules that some testers don't have installed,
or your module is just not compatible with certain platforms. The
relevant section from the Test::Reporter docs has been clipped:
http://clipmarks.com/clipmark/1CCE9BCC-8444-4985-8C46-616EC7CBCFB4/
Although you didn't say what module you were talking about, my ESP tells
me that it's here: http://search.cpan.org/~jtt/File-Fcntl_Lock-0.07/
You gave my ESP a workout ;-) , but I would've preferred that the link
was in your message.
Perhaps fcntl(2) is missing on Cygwin and Freebsd.
As far as bothering the testers is concerned, I wouldn't bother them.
Make your tests more exacting and more descriptive and read Test::Reporter.
| 
XML Sitemap