It appears the real culprit is that DateTime::TimeZone 0.06 failed on make
test:
t/02basic....ok 1468/1478Can't locate object method "utc_year" via package "DateTime"
(perhaps you forgot to load "DateTime"?) at
/home/users/tmp/wilcoxon/.cpan/build/DateTime-TimeZone-0.06/blib/lib/DateTime/TimeZone/America/Chicago.pm
line 1834.
# Looks like you planned 1478 tests but only ran 1468.
# Looks like your test died just after 1468.
t/02basic....dubious
Test returned status 255 (wstat 65280, 0xff00)
DIED. FAILED tests 1469-1478
Failed 10/1478 tests, 99.32% okay
Any ideas what's wrong with this (perl 5.6.1 on Solaris 2.6)?
In any case, t/05tz of DateTime tests reached 40% cpu and 1.4GB of memory
and seemed to stick on test 24 before I killed it. Maybe we should add an
early test making sure that DateTime::TimeZone is the right version
(assuming the older version caused the huge memory usage)?
I thought that a prereq failing to install would cause the "parent" to
fail? In this case, DateTime::TimeZone 0.06 was (attempted) installed as
a prereq of DateTime 0.06.
