First, how useful would be that indication whether a module gets PASS or FAIL ?

All a FAIL means is that the module failed to build on the particular tester's machine. That could mean there's something wrong with the module ... or it could also mean that there's something wrong with the tester's build environment.

I have some modules that rely on external C libraries - and I'm always getting FAIL reports from testers because they don't have the requisite C library installed, or because their version of the requisite C library is too old.

jettero mentioned Devel::CheckLib - and it can, under some circumstances, help out with that. But it entails adding extra cruft to the Makefile.PL, and I would prefer to *not* do that. On too many occasions I've had to work through a Makefile.PL, trying to fix code that has been introduced solely for the purpose of avoiding FAIL reports from testers. Often I've found that once that code has been removed, the module builds flawlessly for me. That's very frustrating - the author has put obstacles in my path out of the (misplaced) vanity of wanting to avoid "FAIL" reports from testers. That's a crime that I would like to avoid. (Not everyone shares my view on this :-)

Cheers,
Rob

In reply to Re: Need advice about CPAN tests by syphilis
in thread Need advice about CPAN tests by dk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.