I'd be interested to see 2 reports indicative of that.

The two reports linked in my original post: both showed linux 3.16.0-4-amd64 debian 3.16.7-ckt25-2 (2016-04-08) with gccversion='4.9.2', libc=libc-2.19.so, and gnulibc_version='2.19', the only difference being 5.20.1 vs 5.22.0. But as stevieb replied, it's probably the improved NaN handling in 5.22 which fixed the bug. (Which then surprises me that my ancient linux perl v5.8.5 passed... but then again, there were probably other NaN handling changes in Perl or differences between the systems/compilers).

excerpts from the fail reports in the spoiler

<Reveal this spoiler or all in this thread>

In reply to Re^4: 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.