RFR: 8098547: (tz) Support tzdata2015e

[Naoto Sato]

Hi Attila,

Looks like it's a regression caused by the fix to 8008577, where the 
default locale data switched to Unicode Consortium's CLDR. Would you 
please file an issue?

Naoto

On 6/25/15 5:49 AM, Attila Szegedi wrote:
> Yeah, basically instantiating a JavaScript native Date object with (70, 0, -10) and confirming it ends up being 10 days before epoch…
> This test failure happened tonight with jdk9, see <http://sthci.se.oracle.com/job/nashorn/ <http://sthci.se.oracle.com/job/nashorn/>>, so I presumed it has to be related (no changes to nashorn itself were made). It’s just suddenly the timezone is named “CEST” instead of “CET”.
>
>> On Jun 25, 2015, at 1:02 PM, Seán Coffey <sean.coffey at oracle.com> wrote:
>>
>> That looks like a strange failure Attila. The timezone in use for that testcase is Europe/Vienna.
>> 2015e tzdata changes haven't been pushed to jdk9-dev forest yet.
>>
>> Where the 1969 date coming from ? Is there some rollover calculation happening ?
>>
>> Regards,
>> Sean.
>>
>> On 25/06/2015 09:05, Attila Szegedi wrote:
>>> FWIW, he do have one new test failure in Nashorn now, it seems related. Can you confirm it is caused by your changes?
>>>
>>> [testng] Test test/script/basic/NASHORN-627.js failed at line 1 -
>>>     [testng]   expected: 'Sun Dec 21 1969 00:00:00 GMT+0100 (CET) -954000000 1969-12-20T23:00:00.000Z'
>>>     [testng]      found: 'Sun Dec 21 1969 00:00:00 GMT+0100 (CEST) -954000000 1969-12-20T23:00:00.000Z'
>>>
>>> Attila.
>>>
>>>> On Jun 24, 2015, at 1:05 PM, Aleksej Efimov <aleksej.efimov at oracle.com> wrote:
>>>>
>>>> Hello,
>>>>
>>>> Please, review the latest tzdata (2015e) [1] integration to JDK9: http://cr.openjdk.java.net/~aefimov/tzdata/2015e/9/0
>>>> Testing shows no TZ related failures on all platforms.
>>>>
>>>> With Best Regards,
>>>> Aleksej
>>>>
>>>> [1] https://bugs.openjdk.java.net/browse/JDK-8098547
>>
>