I'll reply to this post, giving details of the solution I used when I find that solution.Avoiding constants in the test-executable seems to have done the trick, and I can understand how that would have worked.
At least, there have been no FAIL reports from any NetBSD machines (and only one FAIL all up.).
However, I was expecting that the NetBSD FAIL reports should have been replaced with UNKNOWN NetBSD reports.
The Makefile.PL should be doing an "exit 0;", and an "exit 0;" from the Makefile.PL is supposed to result in an UNKNOWN report, isn't it ? But there have been *no* reports at all from NetBSD.
So, I don't really know that my current version of the module has even been looked at by a NetBSD machine. (In the past, the NetBSD reports have begun filtering through within 24 hours, but that doesn't really count for much.)
Cheers,
Rob
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.