On Mon, 14 Jul 2014, Frank Shearar wrote:

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

It's unrelated to the VM. DateAndTime >> #readFrom: (since 7/5/2012) will 
create an object in the local timezone if no timezone is specified. The 
test and some related methods' comments expect it to be in UTC.
The test is rather new, and I think it has always been failing.


Levente

>
> frank
>
>