Summary: | REGRESSION: 2 test262/test/language/statements/async-function failures | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Ryan Haddad <ryanhaddad> | ||||
Component: | JavaScriptCore | Assignee: | GSkachkov <gskachkov> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | buildbot, commit-queue, gskachkov, jlewis3, keith_miller, mark.lam, msaboff, saam, webkit-bug-importer, ysuzuki | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | WebKit Nightly Build | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=175210 | ||||||
Attachments: |
|
Description
Ryan Haddad
2017-08-08 11:34:45 PDT
These failures started after https://trac.webkit.org/r220323 landed. Ohh, I did not expect that async function check that there is no async generator I'll provide patch (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. Created attachment 317688 [details]
Patch
Patch
Comment on attachment 317688 [details]
Patch
r=me
Comment on attachment 317688 [details] Patch Clearing flags on attachment: 317688 Committed r220449: <http://trac.webkit.org/changeset/220449> All reviewed patches have been landed. Closing bug. |