From: jochen@chromium.org Date: Fri, 28 Feb 2014 14:16:50 +0000 (+0000) Subject: Update README about where the test262 files are downloaded from. X-Git-Tag: upstream/4.7.83~10522 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=227cac3bf13876b667e4e68b66361e531df9206c;p=platform%2Fupstream%2Fv8.git Update README about where the test262 files are downloaded from. BUG=none TBR=jkummerow@chromium.org LOG=n Review URL: https://codereview.chromium.org/184573003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@19620 ce2b1a6d-e550-0410-aec6-3dcde31c8c00 --- diff --git a/test/test262/README b/test/test262/README index 680ab77..e975fbb 100644 --- a/test/test262/README +++ b/test/test262/README @@ -2,13 +2,15 @@ This directory contains code for binding the test262 test suite into the v8 test harness. To use the tests check out the test262 tests from - http://hg.ecmascript.org/tests/test262 + https://github.com/tc39/test262 -at revision 365 as 'data' in this directory. Using later version -may be possible but the tests are only known to pass (and indeed run) +at revision 365 (hash fbba29f) as 'data' in this directory. Using later +version may be possible but the tests are only known to pass (and indeed run) with that revision. -hg clone -r 365 http://hg.ecmascript.org/tests/test262 data + git clone https://github.com/tc39/test262 data + cd data + git checkout fbba29f 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