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

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

This isn't even getting to the test case. This is happening when running the make, and Xcode isn't directly used by the module, or indirectly as far as I can tell. As far as I was able to find, this was an issue with "make" being a utility from apple that hadn't been configured yet which is why I figured I might want to follow up...

Comment on Re^2: Odd test report, how to address?

Replies are listed 'Best First'.
Re^3: Odd test report, how to address? by boftx (Deacon) on Nov 13, 2013 at 04:31 UTC
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.	[reply] [d/l]
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]
Re^5: Odd test report, how to address? by boftx (Deacon) on Nov 13, 2013 at 05:26 UTC
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]
Re^6: Odd test report, how to address? by syphilis (Archbishop) on Nov 13, 2013 at 06:39 UTC
Re^7: Odd test report, how to address? by boftx (Deacon) on Nov 13, 2013 at 06:43 UTC
Re^7: Odd test report, how to address? by einhverfr (Friar) on Nov 13, 2013 at 07:24 UTC

In Section Seekers of Perl Wisdom