REGRESSION: 2 test262/test/language/statements/async-function failures

[Ryan Haddad]

test262.yaml/test262/test/language/statements/async-function/early-errors-no-async-generator.js.default: ERROR: Unexpected exit code: 3
test262.yaml/test262/test/language/statements/async-function/early-errors-no-async-generator.js.default-strict: ERROR: Unexpected exit code: 3
FAIL: test262.yaml/test262/test/language/statements/async-function/early-errors-no-async-generator.js.default-strict
FAIL: test262.yaml/test262/test/language/statements/async-function/early-errors-no-async-generator.js.default

https://build.webkit.org/builders/Apple%20El%20Capitan%20Release%20Test262%20%28Tests%29/builds/3197

[Ryan Haddad]

These failures started after https://trac.webkit.org/r220323 landed.

[GSkachkov]

Ohh, I did not expect that async function check that there is no async generator
I'll provide patch

[Yusuke Suzuki]

(In reply to GSkachkov from comment #2)
> Ohh, I did not expect that async function check that there is no async
> generator
> I'll provide patch

I think it's safe to make useAsyncIterator false until you finish async iterator work.
In that case, you can specify @skip for async iterator JSTests for now.

After your work is finished, you can set/remove useAsyncIterator flag. And you can specify :failDueToOutdatedOrBadTest in test262.yaml.

[GSkachkov]

Created attachment 317688 [details]
Patch

Patch

[Yusuke Suzuki]

Comment on attachment 317688 [details]
Patch

r=me

[WebKit Commit Bot]

Comment on attachment 317688 [details]
Patch

Clearing flags on attachment: 317688

Committed r220449: <http://trac.webkit.org/changeset/220449>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.

[Radar WebKit Bug Importer]

<rdar://problem/33795638>