419ca34349
As of the normative change [1] of spec, the export name can be arbitrary strings. Element accesses on module namespace objects will be interpreted as indexed properties, so those element key exports should be setup as elements. [1]: https://github.com/tc39/ecma262/pull/2154 Bug: v8:11690 Change-Id: I3b724d11b9306739268fc5348bae87911a8da18c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3219945 Reviewed-by: Shu-yu Guo <syg@chromium.org> Commit-Queue: legendecas <legendecas@gmail.com> Cr-Commit-Position: refs/heads/main@{#77581} |
||
|---|---|---|
| .. | ||
| local-tests/test | ||
| BUILD.gn | ||
| detachArrayBuffer.js | ||
| harness-adapt-donotevaluate.js | ||
| harness-adapt.js | ||
| harness-agent.js | ||
| harness-ishtmldda.js | ||
| OWNERS | ||
| prune-local-tests.sh | ||
| README | ||
| test262.status | ||
| testcfg.py | ||
| upstream-local-tests.sh | ||
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.