ICU 62 should be released soon. Let's update ICU in Chrome.
Before we do that, I can temporarily update Emoji data to v11 again.
Mind if I assign this to you, Jungshik?
The above ICU bug was resolved. There are a few more failures to investigate and take care of.
One of them is bug 856113. I put a work-around for the latest PS in the CL above.
issue v8:7825 (v8 side of ICU udpate) has more information, too.
https://chromium-review.googlesource.com/c/chromium/src/+/1111818 : chromium-canary:
Now we're down to a few test failures related to bug 856947. Because bug 856947 is not likely to be fixed soon, I'll come up with a temporary work around.
v8 trybots all pass except for node.js bot. The cause for that is known (node.js has its own copy of ICU and node.js bot fails to build Node when there's a version mismatch between v8's ICU and node's ICU).
Down to these tests. They're all related to bug 856947.
blink_platform_unittests (retry summary)
failures:
TextBoundariesTest.ForwardWhitespaces
webkit_unit_tests (retry summary)
failures:
StateMachineUtilTest.IsGraphmeBreak_EmojiModifier
EditingUtilitiesTest.uncheckedPreviousNextOffset
> blink_platform_unittests (retry summary)
> TextBoundariesTest.ForwardWhitespaces
> webkit_unit_tests (retry summary)
> StateMachineUtilTest.IsGraphmeBreak_EmojiModifier
Expected results are updated to Unicode 11 / the latest UAX 29.
Now it's down to EditingUtilitiesTest.uncheckedPreviousNextOffset
For Chromium, it's fixed.
v8 roll is blocked by Node.js issue. I'll mark this as closed. Node.js issue will be resolved when Node.js updates its ICU. v8 in Chrome browser will have ICU 62.1.
Comment 1 by drott@chromium.org
, Jun 7 2018