First, on both Solaris 2.6 (Ultra-2) and FreeBSD 4.6.2 (P2-233) under perl
5.6.1, DateTime::TimeZone fails make test with:
t/01load.....ok
t/02basic....ok 1468/1478Can't locate object method "utc_year" via package "DateTime"
(perhaps you forgot to load "DateTime"?) at
/home/.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
t/03link.....ok
t/04local....ok
After that failure, DateTime still tries to build and has the following
problems:
On Solaris, it "sticks" on t/05tz test 24 and uses about 1.3GB or memory
and 40% of the cpu.
On FreeBSD, it fails with the following (probably as a result of only
having DateTime::TimeZone 0.05):
t/00load..........ok
t/01sanity........ok
t/02last_day......ok
t/03components....ok
t/04epoch.........ok
t/05set...........ok
t/05tz............NOK 25# Failed test (t/05tz.t at line 150)
# got: '2050 063019 CDT'
# expected: '2050 07 1 1 CDT'
The 'year' parameter to DateTime::last_day_of_month was an 'undef', which is not one
of the allowed types: scalar
at /usr/local/lib/perl5/site_perl/5.6.1/DateTime/TimeZone/OlsonDB.pm line 197
# Looks like you planned 65 tests but only ran 25.
# Looks like your test died just after 25.
t/05tz............dubious
Test returned status 255 (wstat 65280, 0xff00)
DIED. FAILED tests 25-65
Failed 41/65 tests, 36.92% okay
t/06add...........ok
t/07compare.......ok
t/09greg..........ok 34/35# this may take a minute...
t/09greg..........ok
t/10subtract......ok
t/11duration......ok
t/12week..........ok
t/13strftime......ok
t/14language......ok
t/15jd............ok
