2a609e4592
Add a second implementation of BalanceDuration which the nanoseconds could be very large and beyong the precision could be handled by double and passed in by BigInt, and values of other time fields are 0. Bug: v8:11544 Change-Id: Ib794c6c78b81b8338434314fa5033cf1e991d32b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3781117 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/main@{#81876} |
||
---|---|---|
.. | ||
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.