v8/test/test262
ulan dd3f1ecf71 Revert of Make dates default to the local timezone if none specified (https://codereview.chromium.org/1229903004/)
Even though the change is ES6 spec compliant, we decided to revert
to be consistent with other browsers and work on fixing the spec.

Original issue's description:
> Make dates default to the local timezone if none specified
>
> In ES5, dates were supposed to default to UTC if no timezone was specified. However, this changed in ES6, which specified that dates should be in the local timezone if no timezone was specified. This CL updates our behavior to match that part of the ES6 spec.

> BUG=chromium:391730, v8:4242
> LOG=Y

> Committed: https://crrev.com/f06754a8e1d305a43560705f6c167d85d40e602d
> Cr-Commit-Position: refs/heads/master@{#29854}

BUG=chromium:543320,chromium:539813
LOG=NO

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

Cr-Commit-Position: refs/heads/master@{#31295}
2015-10-15 12:18:16 +00:00
..
harness-adapt.js [test] Copy test262-es6 into test262. 2015-09-25 13:03:36 +00:00
README [test] Pull test262 as a dependency. 2015-10-08 14:40:52 +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 Revert of Make dates default to the local timezone if none specified (https://codereview.chromium.org/1229903004/) 2015-10-15 12:18:16 +00:00
testcfg.py [Interpreter]: Add fake support for try/catch/finally. 2015-10-15 10:35:31 +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 hash 26e6fd7 (2015/10/01 revision) 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 that 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.