v8/test/test262
cwhan.tunz 8c2af03791 Use internal byteOffset in TypedArray.prototype.set
Since byteOffset is configurable, we need to access byteOffset by
%_ArrayBufferViewGetByteOffset, instead of accessing .byteOffset
property.

BUG=v8:6120

Review-Url: https://codereview.chromium.org/2761673003
Cr-Commit-Position: refs/heads/master@{#44347}
2017-04-03 15:21:18 +00:00
..
local-tests/test Use internal byteOffset in TypedArray.prototype.set 2017-04-03 15:21:18 +00:00
archive.py Reland of [test] Speculatively remove local-tests from archive (patchset #1 id:1 of https://codereview.chromium.org/2640223003/ ) 2017-02-28 14:43:15 +00:00
BUILD.gn [gn] Port test262 archiving to gn 2016-06-06 08:56:58 +00:00
detachArrayBuffer.js test262 roll 2017-03-13 14:33:07 +00:00
harness-adapt.js test262 roll 2017-03-13 14:33:07 +00:00
harness-agent.js test262 roll 2017-03-13 14:33:07 +00:00
list.py test262 roll 2017-03-13 14:33:07 +00:00
prune-local-tests.sh test262 roll 2017-02-10 19:05:55 +00:00
README Make test262 README file revision independent. 2015-11-04 10:52:44 +00:00
test262.gyp test262 roll 2016-10-20 10:29:28 +00:00
test262.isolate Reland of [test] Speculatively remove local-tests from archive (patchset #1 id:1 of https://codereview.chromium.org/2640223003/ ) 2017-02-28 14:43:15 +00:00
test262.status [async-iteration] implement AsyncGenerator 2017-03-29 17:33:12 +00:00
testcfg.py test262 roll 2017-03-13 14:33:07 +00:00
upstream-local-tests.sh test262 roll 2017-03-13 14:33:07 +00:00

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.