On Wed, 19 Feb 2003, Stephen R. Wilcoxon wrote:

> 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)?

Wow, that's a lot! ;)

I'd bet it's the older version.  At least on my system perl only occupies
4.5 MB by the end of the 05tz test.  I think previous version of
DateTime::TimeZone may have had a bug that could cause it to enter an
endless loop in which it generated lots of data.

> 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.

I'll try to fix this.


-dave

/*=======================
House Absolute Consulting
www.houseabsolute.com
=======================*/

Reply via email to