a1e6efd80c
Fix several edge cases consistency issues with ICU discovered by test262 test by using Intl Enumeration API 1. Work around ICU short coming of always fallback in currency display name so when the fallback is "none" in DisplayNames, the force fallback code will produce the correct undefined from the of(currency_code) method. 2. Always check numbering system is not algorithm based numbering system to fix DateTimeFormat/RelativeTimeFormat/NumberFormat resolvedOptions().numberingSystem when the reqested numberingSystem is one of the numbering systems that we filter out the resources and not supported. 3. Generalize the iso8601 bit solution in DateTimeFormat and rename it to alt_calendar bit to also fix DateTimeFormat resolvedOptions report calendar as "islamic" while requesting "islamic-rgsa". 4. Work around reporting inconsistency of currency code and display name in ICU. Bug: v8:12209 Change-Id: Ibd349ee55426fad7d6f20a5e93fb35ff7438e111 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3153576 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by: Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/main@{#77242} |
||
---|---|---|
.. | ||
local-tests/test | ||
BUILD.gn | ||
detachArrayBuffer.js | ||
harness-adapt-donotevaluate.js | ||
harness-adapt.js | ||
harness-agent.js | ||
harness-ishtmldda.js | ||
OWNERS | ||
prune-local-tests.sh | ||
README | ||
test262.status | ||
testcfg.py | ||
upstream-local-tests.sh |
This directory contains code for binding the test262 test suite into the v8 test harness. The tests are checked out as a dependency from https://chromium.googlesource.com/external/github.com/tc39/test262 at a revision specified in the DEPS file as 'data' in this directory. They are fetched with 'gclient sync'. To update to a newer version, please change the DEPS file. Using a newer version, e.g. 'deadbeef' may be possible but the tests are only known to pass (and indeed run) with the DEPS revision. Example: cd data git fetch git checkout deadbeef If you do update to a newer revision you may have to change the test harness adapter code since it uses internal functionality from the harness that comes bundled with the tests. You will most likely also have to update the test expectation file.