v8/test/test262
mythria 47d7ae1154 [Interpreter] Pass correct closure argument when creating block context.
After this change, https://codereview.chromium.org/1475383002 we should
not pass Smi 0 for a closure and expect runtime to look it up. We should
pass the correct argument always.

BUG=v8:4280
LOG=N

Review URL: https://codereview.chromium.org/1558153002

Cr-Commit-Position: refs/heads/master@{#33117}
2016-01-05 15:35:33 +00:00
..
harness-adapt.js [test] Copy test262-es6 into test262. 2015-09-25 13:03:36 +00:00
README Make test262 README file revision independent. 2015-11-04 10:52:44 +00:00
test262.gyp [swarming] Isolate test262. 2015-10-14 08:44:27 +00:00
test262.isolate [swarming] Isolate test262. 2015-10-14 08:44:27 +00:00
test262.status [Interpreter] Pass correct closure argument when creating block context. 2016-01-05 15:35:33 +00:00
testcfg.py [Interpreter]: Add ignition blacklist to mjsunit.status and test262.status. 2015-11-06 18:52:51 +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.