The above is terrible advice.

The tests are there for a reason: to alert you to problems or potential problems. While it is true that you can install and use modules when not all their tests pass, how will you know which test failures are safe to ignore?

First you should investigate which test (s) is/are failing, then look at them to see what the significance is. Observe the log and then when you see a test reported as failing, go right to that test file and run it again, with the verbose flag, and see what it says as output. If that doesn't enlighten you, read the source for the test. If you don't get it, post a question on the module's support page. After one of these steps maybe you'll be able to conclude that the test is not that important and you can install the module anyway. Or, maybe you'll see that your system is incompatible with the version you are installing, or there's a missing linked C library or something like that.

But simply to ignore test failures while building software, because there are just a few of them or for any other reason, is just completely stupid.

The way forward always starts with a minimal test.

In reply to Re^4: Perl-5.22.1 in ARM system (Ignoring test failures is stupid) by 1nickt
in thread Perl-5.22.1 in ARM system by Anonymous Monk

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.