The CPAN Testers Wiki has some information which may be relevant.

Yeah, I did skim through that document.
It tells me how to deal with *my* fuck-ups, but doesn't offer much wrt dealing with *their* fuck-ups.
I guess all one can do is contact the tester and file a bug report ... then wait for an improvement.

Ken, if I were to take a leaf out of your book I would probably begin each test script with something like: 
eval {require Math::MPFR};

[download]
and then skip all tests if Math::MPFR failed to load.
That would certainly avoid the FAILs that are the subject of this thread, but it seems to me that it would also be an act of deception on my part.
I'd be getting a PASS without any of the tests actually being run - and without any guarantee that any of the tests would have passed if only Math::MPFR had been found.

For your scenario, my impression is that if an X server is needed, you should be testing for its existence in the Makefile.PL.
If it's there, than the build process (including the running of all tests) continues.
If it's not there, then the Makefile.PL does an immediate exit 0; and you end up with an NA report (or maybe no report at all).
The risk there would be that an X server is present, but the Makefile.PL fails to detect it and does the exit 0; mistakenly. That wouldn't bother the cpan-testers, though it might bother a potential user.
But giving yourself a PASS just because the X server isn't present is a bit cheeky IMHO.

Anyway - I didn't examine your scenario properly, and you probably know far better than I precisely what *you* ought to be doing :-)

Cheers,
Rob

In reply to Re^2: PREREQ_PM ignored by cpan-tester by syphilis
in thread PREREQ_PM ignored by cpan-tester by syphilis

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.