> On 19 Mar 2016, at 14:25, Bert Freudenberg <bert at freudenbergs.de> wrote:
> 
> On 19.03.2016, at 11:40, Max Leske <maxleske at gmail.com <mailto:maxleske at gmail.com>> wrote:
>> 
>> On 19 Mar 2016, at 08:49, squeak-dev-request at lists.squeakfoundation.org <mailto:squeak-dev-request at lists.squeakfoundation.org> wrote:
>>> 
>>> And Max’s tests might work again, too, without manual preference fiddling.
>> 
>> Yes, that fixes my problem. I still needed to make a small adaptation to reset the value of #automaticTimezone to the value used before the tests but that’s no issue.
> 
> Well … if we could, I’d like to automate this, too. 
> 
> Does the test save the previous time zone value, and restore it after?

No, but it should, now that you mention it. Currently I save the #automaticTimezone value and restore it. Storing and restoring the time zone instead makes more sense since that will also work in Pharo (where, I realise now, this test actually modifies the current time zone without restoring it to the original value).

> 
> If that’s the case we might re-enable the automatic time zone on the restore operation.

Sounds reasonable. So #automaticTimezone would be set to true if #localTimezone == the actual local timezone.

> 
> - Bert -
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20160319/21878bc0/attachment.htm