eeda283e6a
Add flags for https://github.com/tc39/test262/pull/1225 https: //chromium.googlesource.com/external/github.com/tc39/test262/+log/2682ab5..a919d53 Bug: v8:7834 Change-Id: I059b1c712b5b82186a5d438051cb7f043322b315 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1616541 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by: Mathias Bynens <mathias@chromium.org> Cr-Commit-Position: refs/heads/master@{#61592} |
||
---|---|---|
.. | ||
local-tests/test | ||
BUILD.gn | ||
detachArrayBuffer.js | ||
harness-adapt-donotevaluate.js | ||
harness-adapt.js | ||
harness-agent.js | ||
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.