Thanks. I had looked at a couple of the reports, and had seen that it was a sign issue on the NaN: specifically, my expected value is the wrong sign (at least on the instances I dug into), which means it's somewhere in the way I produce my expected value (I probably should've just hardcoded the expected, once I knew what my test matrix looked like).

The last I'd looked, the Windows 5.16.0 failure hadn't shown up in the matrix. That should make it easier to replicate, since it is just a strawberry that I should be able to download tomorrow.

Again, thanks.

In reply to Re^2: Advice wanted for debugging CPAN Testers failures by pryrt
in thread Advice wanted for debugging CPAN Testers failures by pryrt

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.