On Sun, Feb 05, 2012 at 05:36:12PM -0500, David T. Lewis wrote:
> On Sun, Feb 05, 2012 at 02:51:08PM -0600, Chris Muller wrote:
> > > I'm sorry -- I forgot to tell everyone: ?After loading, please run the
> > > following expression:
> > >
> > > ? ? ?TimeZone withAllSubclassesDo: [ : each | each initialize ]
> > 
> > Timespan "arrrgh!" withAllSubclassesDo: [ : each | each initialize ]
> 
> Ah, that's much better :) The errors are gone now, and failures reduced.
> 
> I am getting five failures in TimeTransformTest. This is not unexpected,
> as the tests are from the TimeZoneDatabase package and I would fully expect
> to need to modify that if any time and date classes change in the image.
> 
> I see six remaining failures in DateAndTimeLeapTest and one in one in
> StopWatchTest. I'll try to debug and give you some feedback some time
> after the SuperBowl ... in other words, probably not today ;-)

A bit more feedback on test failures. If I set my time zone to UTC like this:

	"DateAndTime localTimeZone: TimeZone default"

Then I see six failures in DateAndTimeLeapTest and one failure if StopwatchTest
as described above.

However, if I set my time zone to my current offset from UTC like this:

	DateAndTime localTimeZone: (TimeZone
		offset:  (Duration minutes: Locale current offsetLocalToUTC)
		name: 'Local Time'
		abbreviation: 'LT').

Then in addition to those failures, I also see ten failures in TimeStampTest,
one failure in DateTest, and one failure in YearTest.

The failures overall seem to be related to comparing objects that have
an offset from UTC (derived from the time zone offset) to objects that
have zero offset.

I am five hours from UTC, but presumably similar results would be seen
in any time zone with a non-zero offset.

Dave