v8/test262 at 0d65554c057512d39d04e443a79ba5c54697be9d - v8

History

machenbach 0d65554c05 [gn] Port test262 archiving to gn This calls the action that archives test262 in gn. In gn we can't specify an action output outside the product directory. This works around it with an extra action stamp file in the product directory, while the archive remains in the test directory. We don't want to generate the archive in the product directory, as some legacy archiving scripts might include it and it's too large. It should only be included in the swarming tasks that are going to use it for testing. BUG=chromium:474921 Review-Url: https://codereview.chromium.org/2034713005 Cr-Commit-Position: refs/heads/master@{#36731}		2016-06-06 08:56:58 +00:00
..
archive.py	[gn] Port test262 archiving to gn	2016-06-06 08:56:58 +00:00
BUILD.gn	[gn] Port test262 archiving to gn	2016-06-06 08:56:58 +00:00
detachArrayBuffer.js	Detach ArrayBuffer in test262	2016-04-20 19:44:05 +00:00
harness-adapt.js	[test] Copy test262-es6 into test262.	2015-09-25 13:03:36 +00:00
list.py	[Swarming] Speed up test262 upload/download.	2016-02-19 14:41:29 +00:00
README	Make test262 README file revision independent.	2015-11-04 10:52:44 +00:00
test262.gyp	[gn] Move build to gypfiles	2016-04-29 10:11:11 +00:00
test262.isolate	test262 roll	2016-05-02 23:02:38 +00:00
test262.status	[test] Remove obsolete status file entries.	2016-05-30 13:22:51 +00:00
testcfg.py	Detach ArrayBuffer in test262	2016-04-20 19:44:05 +00:00

README

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.