On Thu, 28 Feb 2013 04:53:21 +0100, David Oswald <[email protected]>
wrote:
The FAIL I'm having trouble understanding is this report for
Bytes::Random::Secure:
http://www.cpantesters.org/cpan/report/2437bd2e-6bf5-1014-a779-df2c4f8d0f8f
It looks from that report like Crypt::Random::Seed is missing. If
that's the case, B::R::S shouldn't even be getting tested, since its
PREREQ_PM specifies Crypt::Random::Seed as a prereq.
I spoke to Dana Jacobsen about it (author of Crypt::Random::Seed). He
provided me with this C::R::S "PASS":
http://www.cpantesters.org/cpan/report/b0ade746-6bf6-1014-b36a-9b2c4f8d0f8f
This appears to be the same smoker, and shows that Crypt::Random::Seed
did install properly.
Is this a smoker misconfiguration? Or have I missed something in
Bytes::Random::Secure?
I can explain this one.
Older Perls have an odd bug that causes $ENV{PERL5LIB} of over 65k chars
to be completely ignored on Windows 7, resulting in a near-empty @INC.
This happens in his case as he's running an automated smoker which does
not actually install dists, but only saves them to cpan/build and adds
them to PERL5LIB. On windows below 7 this does not happen, as the 65k
limit is correct there and the process won't even start before reaching
the perl interpreter code. On higher Perls the limit is observed properly.
So, if you get spurious errors, check their PERL5LIB. If it's massive, ask
the smoker to upgrade to Perl5 16.0 or newer.
Related ticket: https://rt.perl.org:443/rt3/Ticket/Display.html?id=87322
--
With regards,
Christian Walde
