Equally bad advice.
If you haven't ever built a perl with no test failures, you must be doing something wrong. I build perls of all versions all the time and can't remember the last time a core Perl build failed -- it was certainly last century. Perhaps you should consider a real operating system?
As for test failure reports not being addressed, a programmer of your skill should be submitting a patch anyway, but that's irrelevant: while not all bug reports I've filed over the years have resulted in fixes or changes, most have.
Upon closer reading of my post you may detect that I was not urging the OP necessarily to report test failures, but rather to undertake the investigation needed to understand why the test is failing. You think that is bad advice?
Your post makes it seem as if you are advocating the same thing as the anonymous poster: to ignore tests and their output as a matter of course. As I said, that's just stupid.
In reply to Re^6: Perl-5.22.1 in ARM system (And yet expedient; and necessary!)
by 1nickt
in thread Perl-5.22.1 in ARM system
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |