in reply to Re^2: Odd test report, how to address?
in thread Odd test report, how to address?

Given that is the case, then I would definitely go with a note in README and then follow up with the tester. It might be possible to test for this in Makefile.pl before make is ever called, but why bother in an automated environment? It will still be reported as a FAIL.

The answer to the question "Can we do this?" is always an emphatic "Yes!" Just give me enough time and money.

Replies are listed 'Best First'.
Re^4: Odd test report, how to address?
by einhverfr (Friar) on Nov 13, 2013 at 05:16 UTC
    Yeah. I did try to follow up with the tester but the mail bounced. Heh..... I don't like this because it means that these are like ignored warnings....
[reply]

      Look on the bright side, is it worse to have a single FAIL report on cpantesters out of what, a 175? or to announce to the public that you haven't taken care of your licenses properly? :)

      It helps to remember that the primary goal is to drain the swamp even when you are hip-deep in alligators.
[reply]
        But I think that, if anyone, it's the tester (not the OP) who hasn't taken care of the licenses properly - in which case I think the tester should be contacted.

        Seguei Trouchelle (the tester) is generally quite responsive and appreciative, and I think einhverfr should persevere in trying to contact him.

        Cheers,
        Rob
[reply]

In Section Seekers of Perl Wisdom