http://build.squeak.org/job/SqueakTrunkOnSpur/31/testReport/junit/KernelTests.Chronology/DateAndTimeTest/testReadFrom/
shows a not-very-helpful test failure report: Expected
'2002-05-1...etc... but was '2002-05-1...etc....

If build.squeak.org is anything like my machine, that failure might
more profitably be reported as:

Expected '2002-05-16T17:20:00+00:00' but was '2002-05-16T17:20:00+01:00'

from this assertion:

self assert: '2002-05-16T17:20:00+00:00' equals: ' 2002-05-16T17:20'
asDateAndTime printString.

Is this expected (because of changes in datetime primitives)?

frank