Skip Menu |

This queue is for tickets about the Config-Std CPAN distribution.

Report information
The Basics
Id: 17425
Status: resolved
Priority: 0/
Queue: Config-Std

People
Owner: Nobody in particular
Requestors: dmacks [...] netspace.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 0.0.2
Fixed in: 0.901



Subject: 00write.t test 5 fails on perl5.8.1
On OS X, Config-Std-0.0.2 'make test' fails t/00write.t when using perl5.8.1: Failed test (t/00write.t at line 35) because the keys are in the wrong order. Full logs from the fink-driven builds on OS X 10.4 are here: http://fink.opendarwin.org/build/2006-01-17/ppc/logs/config-std-pm581.log http://fink.opendarwin.org/build/2006-01-17/ppc/logs/config-std-pm586.log The same result is seen on an OS X 10.3 machine, where perl5.8.1 is as supplied by Apple and on an OS X 10.4 machine, where perl5.8.1 is supplied by Fink. All tests pass under perl5.8.6 (from fink on the 10.3 machine and from apple on the 10.4 machine).
Subject: 00write.t test 5 fails on perl5.8.1 (Config::Std)
Hi, please pardon late reply. With help of Boston.PM, I have taken over Config::STD maintenance from Damian. In preparation for uploading with updated maintainer info, I am going through the RT queue. This was a known problem with v5.8.1 Hash Randomization for Security, combined with sensibly lazy test design. To avoid implicit key-order dependency of simple write test is non-trivial without a dependency upon the 'read' feature's correctness, which is not desirable in unit tests. If this reappears we'll look at it further. Meantime, I am adding a note on the general PERL_HASH_SEED=0 workaround for v5.8.1 hash issues to the =h1 bugs section. bill
Since hash randomization returned in Perl 5.018, this was fixed under RT 85956. This ticket should have been closed at that time.