For the last "n" versions of DateTime::TimeZone (sorry, don't
recall where it started), I've gotten a CPU-bound huge pause right after...

    ok 1545 - The object isa DateTime::TimeZone
    ok 1546 - name should be UTC
    ok 1547 - should not be floating
    ok 1548 - should be UTC
    ok 1549 - offset should be -18000
    ok 1550 - name should be CDT
    ok 1551 - offset should be -21600
    ok 1552 - name should be CST

Takes about four minutes or so on my fast machine to get to test 1553.

Is this expected?  Is this just an OSX weirdness?

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<[email protected]> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

Reply via email to