Default parameter value for catch binding #1483

…have been replaced + test cleanup and renaming test files for consistency

…revision" proposal. (tc39#1510) Fixes tc39gh-1453

- "CannotSuspendMainAgent" feature was changed to "CanBlockIsFalse" flag - Move annex-b tests into annex-b directory - Update variable names in nonshared-int-views.js tests - Move getReport() call in nan-for-timeout.js to avoid iloop - Update BigInt constructor to match new semantics (tc39/proposal-bigint#138)

…lt-arg" (tc39#1521)

Completes tc39gh-1472

Because these files contain syntax errors, the code they contain is not intended to be executed, and the runtime semantics are therefore irrelevant. Simplify the files by removing the unnecessary code.

Some of these are based on work by André Bargull in <https://bugzilla.mozilla.org/show_bug.cgi?id=1433303>.

typo in constructor Test252Error

- fix mixed up test & info - add Symbol feature - maximize length is 0 - maximize configurability is true

These tests are againt a proposed fix for tc39/ecma262#753 They seem to pass in V8, JSC and SpiderMonkey, though ChakraCore hews slightly closer to the previous specification.

…w filenames

…or" (tc39#1556)

… assertion message

…file date 2018-04-23" https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry

…verifyProperty There's a lot of work like this to do, but not enough time in the day to reach it all.

Previously, the error message generated by failed asynchronous tests was generic and underspecified. Improve the format and explicitly document it in project's interpreting guidelines.

super[super()] should evaluate and resolve super() first

This is based on André Bargull's test case in <https://bugzilla.mozilla.org/show_bug.cgi?id=1464757>.

…g "upstreamed" test material via automaton

Reported by André Bargull in <https://bugzilla.mozilla.org/show_bug.cgi?id=1464758>.

- Invalid: super[super()]. Expects super() to be called prior to super property access.

…s().

Emoji data is now published as part of the Unicode standard itself, and thus follows the same version number. Ref. mathiasbynens/unicode-property-escapes-tests@f302c60. Ref. tc39/ecma262#1218. Ref. tc39/ecma262#1219.

…verifyNotWritable, verifyConfigurable. Fixes tc39gh-1591

As per spec changes (tc39/proposal-string-matchall#35), removed tests related to the removed IsRegExp call. To prevent older implementations (not observing spec change) from passing, added a new test to verify the reduced number of observable calls to IsRegExp. Also fix a misreference in `features` frontmatter.

… file

…ixes tc39gh-1512

…mberingSystem. The spec changed in tc39/proposal-intl-locale#47. The tests for calendar were already correct.

…39#1561)

Ref tc39gh-1531

… index

…pdates to all Atomics.wait tests

In order to satisfy the project's formatting rules, license information was inserted into a number of files where it had been mistakenly omitted by the original contributors [1]. In many cases, the license information did not accurately describe the contributor or the time of contribution. Update the information according to the information provided by the contributors at the time each file was authored: - atomicsHelper.js - a72ee6d - detachArrayBuffer.js - 70c7375 - nans.js - b17ffc0 - nativeFunctionMatcher.js - 6b7cbb5 - proxyTrapsHelper.js d530c87 - regexpUtils.js - 44b40e0 - tcoHelper.js - 4dc81d3 [1] 4ea2931

…parison

* Add Intl.RelativeTimeFormat feature. * Add tests for the shape of the Intl.RelativeTimeFormat API. * fixup! Add tests for the shape of the Intl.RelativeTimeFormat API.

…the LineTerminatorSequence within is either Unicode separator code point. (tc39#1612)

…tc39#1616)

…39#1619)

…#1617) Also fixes multiple issues and bugs in various Atomics tests. CONTRIBUTING.md and INTERPRETING.md: - Add missing description for `CanBlockIsFalse` flag and also introduce `CanBlockIsTrue` flag which is needed for some tests (see below). harness/atomicsHelper.js: - Updated `$262.agent.waitUntil` to clarify it can also be called with BigInt64Array objects. - Added `$262.agent.timeouts` constants to unify the various, inconsistently used timeouts in the Atomics tests. Each timeout constant has a brief description and a usage example to clarify when it should or should not be used. The default values were tested in SpiderMonkey (locally and CI) under various system load levels and should hopefully also be valid for other engines. - Added `$262.agent.tryYield` to yield control from the main thread. The default implementation simply calls `$262.agent.sleep`, but test262 hosts could theoretically provide a different implementation. - Added `$262.agent.trySleep` to replace direct calls to `$262.agent.sleep` from the main thread. Motivation for this function: Some test262 hosts (like browsers) may be able to pause and sleep on the main thread, so they could provide their implementation for `trySleep` which performs a busy-wait or something do nothing. harness/testAtomics.js: - Replace `let`, `arrow-functions`, and `for-of` loops to avoid creating extremely long `features` lists in tests using this helper. Removed `Map`, `WeakMap`, `Set`, and `WeakSet` (these weren't even listed in features.yaml) for the same reason and added the missing `Symbol` entry for this file to features.yaml. - Updated all files including "harness/testAtomics.js" to match the new feature requirements. test/built-ins/Atomics/store/good-views.js and test/built-ins/Atomics/store/bigint/good-views.js: - Replace `arrow-functions` and `for-of` loops with ES5 alternatives. test/built-ins/Atomics/wait/bigint/*.js and test/built-ins/Atomics/wake/bigint/*.js - Some tests were using `BigInt64Array.BYTES_PER_ELEMENT * 8` for the SharedArrayBuffer length, but their non-BigInt counterparts are using `Int32Array.BYTES_PER_ELEMENT * 4`. For consistency and to make it easier to compare the BigInt against the non-BigInt versions, I've changed it to `BigInt64Array.BYTES_PER_ELEMENT * 4`. - Also aligned formatting and statement placement when they differed between the non-BigInt and the BigInt version of a test file. (I've diffed some of the non-BigInt and BigInt files against each other and different formatting was a nuisance.) Test files using `$262.agent.monotonicNow()`: - Moved `$262.agent.report()` calls outside of the block of code measured `$262.agent.monotonicNow()` to avoid measuring how long it takes to execute `$262.agent.report()`. - Without this change some tests failed intermittently in certain test configurations in SpiderMonkey. For example with the flags `--ion-eager -- ion-offthread-compile=off` which forces early Ion compilation on the main thread. The `$262.agent.report()` implementation in the SpiderMonkey test262 host embedding uses a for-loop which was forcefully Ion compiled under these settings. And because Ion compilation can take some time, the test case ran longer than `$262.agent.MAX_TIME_EPSILON` which lead to intermittent failures. Test files using `CanBlockIsFalse` / `CanBlockIsTrue`: - Some of these tests actually expected that the main thread can wait and [[CanBlock]] is `true` for the agent record executing the test. Therefore I've added a new `CanBlockIsTrue` flag and replaced the flags where needed. test/built-ins/Atomics/wait/**/*.js and test/built-ins/Atomics/wake/**/*.js: - Use an atomic counter `RUNNING` in more tests to have better control when a worker agent was actually started. - Replace the various `$262.agent.sleep(/* Sleep X ms to ensure worker actually sleeps */)` calls with the new `$262.agent.tryYield()` function. This `X` was sometimes as low as 10 milliseconds, which is definitely too short for CI systems under heavy load (observed by intermittent CI failures for SpiderMonkey) and sometimes as high as 500 milliseconds, which is probably much longer than needed even when the system is under heavy load. - Removed duplicate strings in assertion messages, presumably from copy-pasting the messages between different files. - Removed extra empty lines at the end of multiple files. test/built-ins/Atomics/wake/bad-range.js, test/built-ins/Atomics/wake/bigint/bad-range.js, and test/built-ins/Atomics/wait/bigint/non-bigint64-typedarray-throws.js: - Removed unnecessary `features` and `includes` from this file. test/built-ins/Atomics/wait/waiterlist-order-of-operations-is-fifo.js and test/built-ins/Atomics/wait/bigint/waiterlist-order-of-operations-is-fifo.js: - The test was actually broken and didn't test what it said it does. This probably explains tc39#1530. - The test wants to ensure the waiterlist is implemented as a FIFO structure. This requires that the waiting agents all wait on the same index position, because the waiterlists are defined by each index. But if the agents wait on different indices, each agent is inserted into a different FIFO structure and therefore we can't observe any FIFO ordering between the agents when they're woken up. - All this requires a bit of synchronization between the main agent and the waiting agent, I hope the added comments help to review these changes. test/built-ins/Atomics/wait/good-views.js: - The agent sends multiple reports to the main agent, but only the first one was read. - This error was introduced during previous refactorings. I've changed it to back to use a while-loop as used in the first version of this file. test/built-ins/Atomics/wait/no-spurious-wakeup-no-operation.js: - Only the BigInt version of this test was present, copied it so we also get code coverage for the non-BigInt case. test/built-ins/Atomics/wait/waiterlist-block-indexedposition-wake.js: - Added extra while loops to avoid intermittent failures when the agent worker haven't started to wait. - This should help to avoid some of the intermittent failures we saw for SpiderMonkey. test/built-ins/Atomics/wake/wake-all-on-loc.js and test/built-ins/Atomics/wake/bigint/wake-all-on-loc.js: - This test was also no longer after previous refactoring sessions. - The "B" agent only waited for 10 milliseconds, which made it likely that it already timed out before the main agent was able to call `Atomics.wake`, which in turn rendered the test useless, because the test case wants to ensure that `Atomics.wake` cannot wake "B". But if "B" was already timed out, it can trivially not be woken by `Atomics.wake`. - Added some safety measure to catch the case when "B" timed out before `Atomics.wake` was called and made it a test error if that happens. test/built-ins/Atomics/wake/count-defaults-to-infinity-missing.js, test/built-ins/Atomics/wake/count-defaults-to-infinity-undefined.js, and test/built-ins/Atomics/wake/undefined-index-defaults-to-zero.js: - Changed the `$262.agent.start()` calls to use a for-loop to avoid code duplication. - (Forgot to undo the code formatting around `assert.sameValue`, still need to change it back.) - Also more while-loops around `Atomics.wake`. - These changes should fix tc39#1529 and tc39#1566. test/built-ins/Atomics/wake/wake-all.js: - Removed "B" worker agent. - Without this removal the test case would be exactly equal to test/built-ins/Atomics/wake/wake-all-on-loc.js. test/built-ins/Atomics/wake/wake-in-order-one-time.js: - Add for-loops to avoid code duplication and make the test more readable. - Make the `Atomics.wake` assertion messages unique by adding the current loop counter. - Add `$262.agent.tryYield()` to give the worker agents enough time to actually start waiting. test/built-ins/Atomics/wake/wake-in-order.js: - Removed the outer loop `attempt < 10` because it uses `$262.agent` in a way currently not required to work. And which actually also doesn't work in SpiderMonkey's implementation of `$262.agent`. - According to INTERPRETING.md `$262.agent.broadcast()` broadcasts its message to all agents ever started by `$262.agent.start()` and then blocks until all agents received the broadcast. It is not required that the agents started by the first `$262.agent.broadcast()` call will all be disabled/destroyed/whatever when the second `$262.agent.broadcast()` call occurs, which then means the second `$262.agent.broadcast()` call still tries to reach the agents started in the first loop iteration, but these may no longer accept broadcasts and therefore won't acknowledge they've received the broadcast. Which then means the second `$262.agent.broadcast()` call waits forever.

…t/webkit.git at sha 949e26452cfa153a7f4afe593da97e2fe9e1b706 on Tue Jul 03 2018 14:35:15 GMT-0400 (Eastern Daylight Time) (tc39#1620) * [javascriptcore-test262-automation] changes from git@github.com:WebKit/webkit.git at sha 949e26452cfa153a7f4afe593da97e2fe9e1b706 on Tue Jul 03 2018 14:35:15 GMT-0400 (Eastern Daylight Time)

The specification changed in tc39/proposal-intl-relative-time#77.

The specification changed in tc39/proposal-intl-list-format#13.

This was added to the specification in tc39/proposal-intl-segmenter#29.

… objects.

…t constructor.

The specification was changed in tc39/proposal-intl-relative-time#79.

The specification was updated in tc39/ecma402#232.

mathiasbynens/unicode-property-escapes-tests@62cbe2f

The document fragments used by the ECMAScript specification do not conform to any particular pattern beyond the grammar defined by the URL standard [1]. Relax the linting rule to enforce a simplified version of that grammar. [1] https://url.spec.whatwg.org/#fragment-state

Promote consistency in coverage by adding new tests that correspond to those that were authored previously.

Verify runtime semantics through assignment to an unresolvable reference, reducing the complexity of tests that previously relied on the semantics of the `eval` function.

Test262 already includes tests to ensure the correct runtime semantics for these forms. Add equivalent tests designed to verify that the equivalent parsing behavior is also observed.

A number of tests for string literals assert the restriction on LegacyOctalEscapeSequence in strict mode code and differ only in the escape sequence under test. Although each is valid, none of the escape sequences are sufficiently distinct from the test 'legacy-octal-escape-sequence-stricts.js' to warrant their inclusion in the test suite. Because that test's use of literal code makes it consumable by parsers and because that test includes much more thorough documentation, it should be preferred. Summary of LegacyOctalEscapeSequences under test in the removed files: test/language/literals/string/7.8.4-10-s.js: eval('var x = " \\10 ";'); test/language/literals/string/7.8.4-11-s.js: eval('var x = "\\16";'); test/language/literals/string/7.8.4-12-s.js: eval('var x = "\\17";'); test/language/literals/string/7.8.4-13-s.js: eval('var x = "\\30";'); test/language/literals/string/7.8.4-14-s.js: eval('var x = "\\31";'); test/language/literals/string/7.8.4-15-s.js: eval('var x = "\\37";'); test/language/literals/string/7.8.4-16-s.js: eval('var x = "\\400";'); test/language/literals/string/7.8.4-17-s.js: eval('var x = "\\411";'); test/language/literals/string/7.8.4-18-s.js: eval('var x = "\\43a";'); test/language/literals/string/7.8.4-19-s.js: eval('var x = "\\463";'); test/language/literals/string/7.8.4-2-s.js: eval('var x = "\\1";'); test/language/literals/string/7.8.4-20-s.js: eval('var x = "\\474";'); test/language/literals/string/7.8.4-21-s.js: eval('var x = "\\77";'); test/language/literals/string/7.8.4-22-s.js: eval('var x = "\\777";'); test/language/literals/string/7.8.4-23-s.js: eval('var x = "\\000";'); test/language/literals/string/7.8.4-24-s.js: eval('var x = "\\001";'); test/language/literals/string/7.8.4-25-s.js: eval('var x = "\\106";'); test/language/literals/string/7.8.4-26-s.js: eval('var x = "\\207";'); test/language/literals/string/7.8.4-27-s.js: eval('var x = "\\377";'); test/language/literals/string/7.8.4-28-s.js: eval('var x = "\\376";'); test/language/literals/string/7.8.4-29-s.js: eval('var x = "\\3760";'); test/language/literals/string/7.8.4-3-s.js: eval('var x = "a\\4";'); test/language/literals/string/7.8.4-32-s.js: eval('var x = "\\1\\1";'); test/language/literals/string/7.8.4-33-s.js: eval('var x = "\\1\\2\\7";'); test/language/literals/string/7.8.4-4-s.js: eval('var x = "z\\7";'); test/language/literals/string/7.8.4-5-s.js: eval('var x = "\\00a";'); test/language/literals/string/7.8.4-6-s.js: eval('var x = "\\01z";'); test/language/literals/string/7.8.4-7-s.js: eval('var x = "a\\03z";'); test/language/literals/string/7.8.4-8-s.js: eval('var x = " \\06";');

This test for string literals asserts the restriction on LegacyOctalEscapeSequence in strict mode. It is not sufficiently distinct from the test 'legacy-octal-escape-sequence-stricts.js' to warrant inclusion in the test suite. Because that test includes much more thorough documentation, it should be preferred.

This test is technically valid because it does trigger a SyntaxError in conforming runtimes. However, it was authored and documented to test LegacyOctalEscapeSequence, but due to an apparent typo, it actually demonstrates an unrelated parsing error. Because 'legacy-octal-escape-sequence-stricts.js' sufficiently tests the restriction on LegacyOctalEscapeSequence, remove this test rather than correct it.

Thsi test for the parsing of string literals was expressed using `eval`. This made the test more complex than necessary and also prevented the test from providing value to ECMAScript parsers. Remove the use of `eval` and instead express the expectation with literal source text.

…LocalesOf()

…ests

…ToParts.

Proxy/deleteProperty/boolean-trap-result-boolean-true.js was missing a feature flag for the Reflect library.

All other Proxy tests use the syntax `attr: function() {...}` for defining traps, ownKeys was unique in using the shorthand syntax. Change to longhand syntax for back-compat for partial implementations.

Follow up to tc39#1643

…ontributed/javascriptcore) (tc39#1629) - Eliminates: - controlFlowProfiler/* - exceptionFuzz/*

Additionally removed the `arrow-function` feature for test/language/eval-code/direct/new.target-fn.js as it is not testing arrow-functions, but they are mentioned in the preamble.

…ted by test262-harness. (tc39#1650) This is not a breaking change, it simply adds explicit handling to the function

The specification was updated in tc39/ecma402#232.

…d resolvedOptions.

…matToParts.

…revision sha's from export and changed files. sourceRevisionAtLastExport: 8bfa53d50 targetRevisionAtLastExport: 8bc4e38

…t to a string. Fixes tc39#1640 Closes tc39#1652

…ebkit/webkit.git at sha 00228d3ccc on Mon Jul 30 2018 18:01:10 GMT+0000 (Coordinated Universal Time)

…revision sha's from export and changed files. sourceRevisionAtLastExport: 00228d3ccc targetRevisionAtLastExport: 4314e2c

I observed each file in each of these folders and they don't contain any test matching for specific parts of ECMAScript, without a specific place for Test262. Ref bocoup/test262-automation#76

These are not spec tests neither identify points not already covered in the tests to cover something new from the specs

…ebkit/webkit.git at sha 5895364ed5 on Fri Aug 03 2018 18:02:54 GMT+0000 (Coordinated Universal Time)

…revision sha's from export and changed files. sourceRevisionAtLastExport: 5895364ed5 targetRevisionAtLastExport: df1fc48

The specification was changed to remove the useGrouping option in <tc39/proposal-intl-relative-time#81>. The change to remove the minimumIntegerDigits option in that PR was already taken into account; this commit also removes the reference to the issue. This also removes some commented-out code that was left in by accident.

Negative tests are the better approach for early error tests. Closes tc39#1622.

This is interesting because Polish has different output for the "short" and "narrow" styles.

…lts.

…pportedLocalesOf(). This is based on test/intl402/NumberFormat/supportedLocalesOf/basic.js.

…uments.

…ebkit/webkit.git at sha b69d88687a on Fri Aug 10 2018 18:07:39 GMT+0000 (Coordinated Universal Time)

…revision sha's from export and changed files. sourceRevisionAtLastExport: b69d88687a targetRevisionAtLastExport: 93b2865

…nts to the constructor.

…gent.MAX_TIME_EPSILON $262.agent.MAX_TIME_EPSILON was intended to be used for callers like `Atomics.wait(typedArray, indexNumber, valueNumber, timeoutNumber)` where all parameters with the `Number` suffix denote values which are already Number values. It should not be used for `Atomics.wait(typedArray, indexObject, valueObject, timeoutObject)` where all parameters with the `Object` suffix denote values which are Object values, because in that case we'd require that `ToNumber(objectValue)` (potentially invoked multiple times) completes in less than 100 milliseconds (the default value for MAX_TIME_EPSILON). Also removes $262.agent.MAX_TIME_EPSILON because it is now no longer used.

…ebkit/webkit.git at sha 3454cfdb5a on Sat Aug 18 2018 18:11:01 GMT+0000 (Coordinated Universal Time)

…revision sha's from export and changed files. sourceRevisionAtLastExport: 3454cfdb5a targetRevisionAtLastExport: 1804b13

# Conflicts: # src/class-fields/init-err-contains-super.case

# Conflicts: # src/class-fields/eval-err-contains-arguments.case # src/class-fields/eval-err-contains-supercall-1.case # src/class-fields/eval-err-contains-supercall-2.case # src/class-fields/eval-err-contains-supercall.case # src/class-fields/eval-err-contains-superproperty-1.case # src/class-fields/eval-err-contains-superproperty-2.case

# Conflicts: # src/class-fields/propname-constructor.case # src/class-fields/propname-error/cls-decl-computed-name.template # src/class-fields/propname-error/cls-decl-literal-name.template # src/class-fields/propname-error/cls-decl-string-name.template # src/class-fields/propname-error/cls-expr-computed-name.template # src/class-fields/propname-error/cls-expr-literal-name.template # src/class-fields/propname-error/cls-expr-string-name.template

# Conflicts: # src/class-fields/propname-error/cls-decl-variable-name.template # src/class-fields/propname-error/cls-expr-variable-name.template

# Conflicts: # src/class-fields/default/cls-decl-after-same-line-async-gen.template # src/class-fields/default/cls-decl-after-same-line-async-method.template # src/class-fields/default/cls-decl-after-same-line-gen.template # src/class-fields/default/cls-decl-after-same-line-method.template # src/class-fields/default/cls-decl-after-same-line-static-async-gen.template # src/class-fields/default/cls-decl-after-same-line-static-async-method.template # src/class-fields/default/cls-decl-after-same-line-static-gen.template # src/class-fields/default/cls-decl-after-same-line-static-method.template # src/class-fields/default/cls-decl-multiple-definitions.template # src/class-fields/default/cls-decl-multiple-stacked-definitions.template # src/class-fields/default/cls-decl-new-no-sc-line-method.template # src/class-fields/default/cls-decl-new-sc-line-generator.template # src/class-fields/default/cls-decl-new-sc-line-method.template # src/class-fields/default/cls-decl-regular-definitions.template # src/class-fields/default/cls-decl-same-line-generator.template # src/class-fields/default/cls-decl-same-line-method.template # src/class-fields/default/cls-decl-wrapped-in-sc.template # src/class-fields/default/cls-expr-after-same-line-async-gen.template # src/class-fields/default/cls-expr-after-same-line-async-method.template # src/class-fields/default/cls-expr-after-same-line-gen.template # src/class-fields/default/cls-expr-after-same-line-method.template # src/class-fields/default/cls-expr-after-same-line-static-async-gen.template # src/class-fields/default/cls-expr-after-same-line-static-async-method.template # src/class-fields/default/cls-expr-after-same-line-static-gen.template # src/class-fields/default/cls-expr-after-same-line-static-method.template # src/class-fields/default/cls-expr-multiple-definitions.template # src/class-fields/default/cls-expr-multiple-stacked-definitions.template # src/class-fields/default/cls-expr-new-no-sc-line-method.template # src/class-fields/default/cls-expr-new-sc-line-generator.template # src/class-fields/default/cls-expr-new-sc-line-method.template # src/class-fields/default/cls-expr-regular-definitions.template # src/class-fields/default/cls-expr-same-line-generator.template # src/class-fields/default/cls-expr-same-line-method.template # src/class-fields/default/cls-expr-wrapped-in-sc.template # src/class-fields/private-names.case

# Conflicts: # test/language/statements/class/classelementname-abrupt-completion.js # test/language/statements/class/fielddefinition-initializer-abrupt-completion.js # test/language/statements/class/super-fielddefinition-initializer-abrupt-completion.js

…target.case

…ting erroneous tests where restrictions do not align.

class-fields-public doesn't apply to all tests that are generated from these templates

…ource

…ses & templates

- needs to use async* to declare async generator methods. - Needs to use yield* if delegating yield semantics are intended. - Has assignment to private name method, which is not allowed and throws a TypeError at runtime. - handle multiple $DONE calls - fix calls to private methods

…ebkit/webkit.git at sha ffc7368147 on Tue Aug 21 2018 18:14:08 GMT+0000 (Coordinated Universal Time)

…revision sha's from export and changed files. sourceRevisionAtLastExport: ffc7368147 targetRevisionAtLastExport: ac84cae

…-constructor-err.js

…ebkit/webkit.git at sha 93457d631e on Wed Aug 22 2018 18:13:32 GMT+0000 (Coordinated Universal Time)

…revision sha's from export and changed files. sourceRevisionAtLastExport: 93457d631e targetRevisionAtLastExport: 04c056b

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Default parameter value for catch binding #1483

Default parameter value for catch binding #1483

Commits on May 14, 2019