Closed Bug 1877862 Opened 2 years ago Closed 5 months ago

New test262 failures with AsyncFromSyncIteratorPrototype

Categories

(Core :: JavaScript Engine, defect, P3)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1610315

People

(Reporter: dminor, Unassigned)

References

(Blocks 1 open bug)

Details

While updating test262 in Bug 1877822, I hit a handful of new failures with AsyncFromSyncIteratorPrototype tests:
test262/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-undefined-poisoned-return.js
test262/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-undefined-return-object.js
test262/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-undefined-return-not-object.js
test262/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-null.js
test262/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-undefined.js
test262/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-result-poisoned-wrapper.js
test262/built-ins/AsyncFromSyncIteratorPrototype/throw/iterator-result-rejected-promise-close.js
test262/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-undefined-get-return-undefined.js
test262/built-ins/AsyncFromSyncIteratorPrototype/next/next-result-poisoned-wrapper.js
test262/built-ins/AsyncFromSyncIteratorPrototype/next/for-await-iterator-next-rejected-promise-close.js
test262/built-ins/AsyncFromSyncIteratorPrototype/next/yield-iterator-next-rejected-promise-close.js
test262/built-ins/AsyncFromSyncIteratorPrototype/next/for-await-next-rejected-promise-close.js
test262/built-ins/AsyncFromSyncIteratorPrototype/next/iterator-result-poisoned-wrapper.js
test262/built-ins/AsyncFromSyncIteratorPrototype/next/yield-next-rejected-promise-close.js

Severity: -- → S4
Priority: -- → P3

Those tests (mostly, at least) correspond to https://github.com/tc39/ecma262/pull/2600. That PR has consensus but isn't landed yet because we've been waiting for implementations.

V8 has begun implementation; you can follow https://bugs.chromium.org/p/v8/issues/detail?id=12594.

Status: NEW → RESOLVED
Closed: 5 months ago
Duplicate of bug: 1610315
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.