|Think about Loose Coupling|
Funky Test Failure, How to Correctby einhverfr (Friar)
|on Feb 23, 2014 at 13:53 UTC||Need Help??|
einhverfr has asked for the
wisdom of the Perl Monks concerning the following question:
I have gotten a really odd test failure on cpantesters.org for PGObject::Type::DateTime. I am not sure if there is anything I can do to keep it from happening again (I really try hard to avoid having any test failures there). It only seems to happen on systems with the exact same software versions as the tester reports. For all I know the failure I saw in 1.00 and the one I saw in 1.00.001 could be from the same system. So it might be only one system failing for all I know.
Perl seems to be complaining about taint mode and the following line in DateTime::Timezone::Floating:
use parent 'Class::Singleton', 'DateTime::TimeZone::OffsetOnly';
(assuming that the module is the same there as on other systems).
I think that it is clear the problem is fairly deep in the dependency tree, so my thinking is that it might be good to test for being able to load the DateTime::TimeZone::Floating module under taint mode and skip the load test if that fails. I am worried about the fact that this might expose other bugs down the line for some users however.
What other options do I have?
Edit: It does look like the same tester in both this and the earlier failure that prompted it.
Update: So this is specific to one (or so) Perl 5.19.6 system. Since 5.19.6 is a development release, I am going to treat it as a Perl bug. I am going to assume that a tester running a development release is doing so for reasons of testing the Perl version as much as anything else and will follow up with him for the narrow purpose of reporting this as a possible Perl 5.19 issue.