Hi Frank,


On Mon, Jul 14, 2014 at 2:11 PM, Frank Shearar <frank.shearar at gmail.com>
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)?
>

This isn't expected.  I got as far as finding out that the difference is
due to Spur answering 1 hour off in DateAndTime class>>localOffset.  That
itself could be as simple as DataAndTime's LocalTimeZone variable not being
flushed.  Because when I evaluate TimeZone default offset I get 0 as
expected.  Alas I'm mired in a performance regression right now so have no
time to look at this yet.

Could be because the Preferences valueOfFlag: #useLocale is false, which it
shouldn't be.
Could be because Locale startUp: isn't evaluated.
-- 
best,
Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20140714/b2ba0225/attachment.htm