Update timezone db to 2017b

Update timezone db to 2017b

See

  http://mm.icann.org/pipermail/tz-announce/2017-March/000046.html


for details.

  - Haiti resumed observing DST.

Data file size changes:

   android/icudtl.dat 6573792 =>  6573872
   common/icudt*.dat 10130480 => 10130560

BUG=473288
TEST=Try the following in d8 or Chrome's JS console:
 > (new Date("3/12/2016 12:00Z")).toLocaleString("en", {timeZone:
 "America/Port-au-Prince"})
 "3/12/2016, 7:00:00 AM"
 > (new Date("3/12/2017 12:00Z")).toLocaleString("en", {timeZone:
 "America/Port-au-Prince"})
 "3/12/2017, 8:00:00 AM"

Committed: https://chromium.googlesource.com/chromium/deps/icu/+/b34251f8b762f8e2112a89c587855ca4297fed96

[jungshik at Google, 2017-04-11 22:15:35]

Description was changed from

==========
Update timezone db to 2017b

See

  http://mm.icann.org/pipermail/tz-announce/2017-March/000046.html


for details.

  - Haiti resumed observing DST.

   android/icudtl.dat 6573024 =>  6573872
   common/icudtb.dat 10129712 => 10130560
   common/icudtl.dat 10129712 => 10130560

BUG=473288
TEST=Try the following in d8 or Chrome's JS console:
 > (new Date("4/4/2017 12:00Z")).toLocaleString("en", {timeZone:
 "Asia/Ulaanbaatar"})
 "4/4/2016, 8:00:00 PM"
 > (new Date("4/4/2016 12:00Z")).toLocaleString("en", {timeZone:
 "Asia/Ulaanbaatar"})
 "4/4/2016, 9:00:00 PM"


BUG=
==========

to

==========
Update timezone db to 2017b

See

  http://mm.icann.org/pipermail/tz-announce/2017-March/000046.html


for details.

  - Haiti resumed observing DST.

   android/icudtl.dat 6573792 =>  6573872
   common/icudt*.dat 10130480 => 10130560

BUG=473288
TEST=Try the following in d8 or Chrome's JS console:
 > (new Date("4/4/2017 12:00Z")).toLocaleString("en", {timeZone:
 "Asia/Ulaanbaatar"})
 "4/4/2016, 8:00:00 PM"
 > (new Date("4/4/2016 12:00Z")).toLocaleString("en", {timeZone:
 "Asia/Ulaanbaatar"})
 "4/4/2016, 9:00:00 PM"


BUG=
==========

[jungshik at Google, 2017-04-11 22:33:46]

Description was changed from

==========
Update timezone db to 2017b

See

  http://mm.icann.org/pipermail/tz-announce/2017-March/000046.html


for details.

  - Haiti resumed observing DST.

   android/icudtl.dat 6573792 =>  6573872
   common/icudt*.dat 10130480 => 10130560

BUG=473288
TEST=Try the following in d8 or Chrome's JS console:
 > (new Date("4/4/2017 12:00Z")).toLocaleString("en", {timeZone:
 "Asia/Ulaanbaatar"})
 "4/4/2016, 8:00:00 PM"
 > (new Date("4/4/2016 12:00Z")).toLocaleString("en", {timeZone:
 "Asia/Ulaanbaatar"})
 "4/4/2016, 9:00:00 PM"


BUG=
==========

to

==========
Update timezone db to 2017b

See

  http://mm.icann.org/pipermail/tz-announce/2017-March/000046.html


for details.

  - Haiti resumed observing DST.

   android/icudtl.dat 6573792 =>  6573872
   common/icudt*.dat 10130480 => 10130560

BUG=473288
TEST=Try the following in d8 or Chrome's JS console:
 > (new Date("3/12/2016 12:00Z")).toLocaleString("en", {timeZone:
 "America/Port-au-Prince"})
 "3/12/2016, 7:00:00 AM"
 > (new Date("3/12/2017 12:00Z")).toLocaleString("en", {timeZone:
 "America/Port-au-Prince"})
 "3/12/2017, 8:00:00 AM"

BUG=
==========

[jungshik at Google, 2017-04-11 22:34:38]

Description was changed from

==========
Update timezone db to 2017b

See

  http://mm.icann.org/pipermail/tz-announce/2017-March/000046.html


for details.

  - Haiti resumed observing DST.

   android/icudtl.dat 6573792 =>  6573872
   common/icudt*.dat 10130480 => 10130560

BUG=473288
TEST=Try the following in d8 or Chrome's JS console:
 > (new Date("3/12/2016 12:00Z")).toLocaleString("en", {timeZone:
 "America/Port-au-Prince"})
 "3/12/2016, 7:00:00 AM"
 > (new Date("3/12/2017 12:00Z")).toLocaleString("en", {timeZone:
 "America/Port-au-Prince"})
 "3/12/2017, 8:00:00 AM"

BUG=
==========

to

==========
Update timezone db to 2017b

See

  http://mm.icann.org/pipermail/tz-announce/2017-March/000046.html


for details.

  - Haiti resumed observing DST.

Data file size changes:

   android/icudtl.dat 6573792 =>  6573872
   common/icudt*.dat 10130480 => 10130560

BUG=473288
TEST=Try the following in d8 or Chrome's JS console:
 > (new Date("3/12/2016 12:00Z")).toLocaleString("en", {timeZone:
 "America/Port-au-Prince"})
 "3/12/2016, 7:00:00 AM"
 > (new Date("3/12/2017 12:00Z")).toLocaleString("en", {timeZone:
 "America/Port-au-Prince"})
 "3/12/2017, 8:00:00 AM"
==========

[jungshik at Google, 2017-04-11 23:08:12]

Description was changed from

==========
Update timezone db to 2017b

See

  http://mm.icann.org/pipermail/tz-announce/2017-March/000046.html


for details.

  - Haiti resumed observing DST.

Data file size changes:

   android/icudtl.dat 6573792 =>  6573872
   common/icudt*.dat 10130480 => 10130560

BUG=473288
TEST=Try the following in d8 or Chrome's JS console:
 > (new Date("3/12/2016 12:00Z")).toLocaleString("en", {timeZone:
 "America/Port-au-Prince"})
 "3/12/2016, 7:00:00 AM"
 > (new Date("3/12/2017 12:00Z")).toLocaleString("en", {timeZone:
 "America/Port-au-Prince"})
 "3/12/2017, 8:00:00 AM"
==========

to

==========
Update timezone db to 2017b

See

  http://mm.icann.org/pipermail/tz-announce/2017-March/000046.html


for details.

  - Haiti resumed observing DST.

Data file size changes:

   android/icudtl.dat 6573792 =>  6573872
   common/icudt*.dat 10130480 => 10130560

BUG=473288
TEST=Try the following in d8 or Chrome's JS console:
 > (new Date("3/12/2016 12:00Z")).toLocaleString("en", {timeZone:
 "America/Port-au-Prince"})
 "3/12/2016, 7:00:00 AM"
 > (new Date("3/12/2017 12:00Z")).toLocaleString("en", {timeZone:
 "America/Port-au-Prince"})
 "3/12/2017, 8:00:00 AM"

Committed:
https://chromium.googlesource.com/chromium/deps/icu/+/b34251f8b762f8e2112a89c...
==========

[jungshik at Google, 2017-04-11 23:08:12]

Committed patchset #1 (id:1) manually as
b34251f8b762f8e2112a89c587855ca4297fed96 (presubmit successful).

[Michael Achenbach, 2017-04-12 07:40:25]

machenbach@chromium.org changed reviewers:
+ machenbach@chromium.org

[Michael Achenbach, 2017-04-12 07:40:25]

FYI: This seems to lead to failures when rolling into V8:
https://chromium-review.googlesource.com/c/475165/

In particular:
https://build.chromium.org/p/tryserver.v8/builders/v8_linux64_rel_ng_triggere...

@littledan: Should we disable the failing tests for now to get the roll through?

[Michael Achenbach, 2017-04-12 07:41:41]

On 2017/04/12 07:40:25, Michael Achenbach wrote:
> FYI: This seems to lead to failures when rolling into V8:
> https://chromium-review.googlesource.com/c/475165/
> 
> In particular:
>
https://build.chromium.org/p/tryserver.v8/builders/v8_linux64_rel_ng_triggere...
> 
> @littledan: Should we disable the failing tests for now to get the roll
through?

I'm not certain that it's from this change. Could be anything in range:
https://chromium.googlesource.com/chromium/deps/icu/+log/450be73..b34251f

[Dan Ehrenberg, 2017-04-12 10:10:21]

On 2017/04/12 07:41:41, Michael Achenbach wrote:
> On 2017/04/12 07:40:25, Michael Achenbach wrote:
> > FYI: This seems to lead to failures when rolling into V8:
> > https://chromium-review.googlesource.com/c/475165/
> > 
> > In particular:
> >
>
https://build.chromium.org/p/tryserver.v8/builders/v8_linux64_rel_ng_triggere...
> > 
> > @littledan: Should we disable the failing tests for now to get the roll
> through?
> 
> I'm not certain that it's from this change. Could be anything in range:
> https://chromium.googlesource.com/chromium/deps/icu/+log/450be73..b34251f

I don't know whether it's this or the ICU roll. I don't see any relevant recent
changes in the tz database FWIW. Either way, the new test outcomes seem
reasonable to me; I'm fine with disabling the tests for you to do the roll, and
then updating the expectations to match the output in a follow-on patch. (FWIW,
tangentially related spec open issue: https://github.com/tc39/ecma402/issues/121
-- we may have to leave the ICU tests marked failing due to this.)

[Michael Achenbach, 2017-04-12 12:23:13]

On 2017/04/12 10:10:21, Dan Ehrenberg wrote:
> On 2017/04/12 07:41:41, Michael Achenbach wrote:
> > On 2017/04/12 07:40:25, Michael Achenbach wrote:
> > > FYI: This seems to lead to failures when rolling into V8:
> > > https://chromium-review.googlesource.com/c/475165/
> > > 
> > > In particular:
> > >
> >
>
https://build.chromium.org/p/tryserver.v8/builders/v8_linux64_rel_ng_triggere...
> > > 
> > > @littledan: Should we disable the failing tests for now to get the roll
> > through?
> > 
> > I'm not certain that it's from this change. Could be anything in range:
> > https://chromium.googlesource.com/chromium/deps/icu/+log/450be73..b34251f
> 
> I don't know whether it's this or the ICU roll. I don't see any relevant
recent
> changes in the tz database FWIW. Either way, the new test outcomes seem
> reasonable to me; I'm fine with disabling the tests for you to do the roll,
and
> then updating the expectations to match the output in a follow-on patch.
(FWIW,
> tangentially related spec open issue:
https://github.com/tc39/ecma402/issues/121
> -- we may have to leave the ICU tests marked failing due to this.)

FYI, filed http://crbug.com/v8/6252 and handling it there.