5138e02ac1
Also add more test cases of Array lastIndexOf with proxy, inspired by test262. In the path for sparse arrays, no changes are needed because element accesses are not observable there (thanks to UseSparseVariant). Bug: v8:7813 Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng Change-Id: Ifd47149f654e92f56d0a1ed6b3debc93718702be Reviewed-on: https://chromium-review.googlesource.com/1160307 Commit-Queue: Hai Dang <dhai@google.com> Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#54887} |
||
---|---|---|
.. | ||
local-tests/test | ||
BUILD.gn | ||
detachArrayBuffer.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.