bb61aa4a02
This is a noop right now as we run test262 without variants on asan. We'll use the status file to whitelist the variants in a synchronous way in v8 after the infra change lands to activate them. Bug: chromium:710428 NOTRY=true Change-Id: I146bbc648775ef0e250c16695b956ecd1d6e105e Reviewed-on: https://chromium-review.googlesource.com/474845 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Daniel Ehrenberg <littledan@chromium.org> Cr-Commit-Position: refs/heads/master@{#44574} |
||
---|---|---|
.. | ||
local-tests/test | ||
archive.py | ||
BUILD.gn | ||
detachArrayBuffer.js | ||
harness-adapt.js | ||
harness-agent.js | ||
list.py | ||
prune-local-tests.sh | ||
README | ||
test262.gyp | ||
test262.isolate | ||
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.