2058720 - test262: built-ins/AsyncIteratorPrototype/Symbol.asyncDispose/invokes-return.js fails under --enable-explicit-resource-management

Status: ASSIGNED

(Core :: JavaScript Engine, task, P3)

Description

[Cornelius | CE student]

While updating the test262 snapshot, the following test regresses
when run with --enable-explicit-resource-management:

test262/built-ins/AsyncIteratorPrototype/Symbol.asyncDispose/invokes-return.js

Failure:
Test262Error: Expected SameValue(«1», «0») to be true

Reproduce:
run the test to reproduce it (other clever ways to reproduce can as well work)

Comment 1

[Matthew Gaudet (he/him) [:mgaudet]]

This is surprising because it's been shipped by default for quite some time now; are we not running this in CI? I've not seen this failure at all?

Comment 2

[Debadree Chatterjee]

Attachment: WIP: Bug 2058720 - Call return() with no arguments from @@asyncDispose.

%AsyncIteratorPrototype% [ @@asyncDispose ] must Call(return, obj, « »).
SpiderMonkey passed « undefined », so iterator.return() observed one
argument and test262 invokes-return.js failed. That test was skipped in
CI when the test262 snapshot landed in bug 2057270.

Call return with an empty argument list, update the jit-test to expect
zero arguments, and unskip the test262 file.