Remove --harmony-async-await runtime flag

Remove --harmony-async-await runtime flag

It shipped with Chrome 55 stable.

R=littledan@chromium.org

Review-Url: https://codereview.chromium.org/2621173002
Cr-Commit-Position: refs/heads/master@{#42203}
Committed: https://chromium.googlesource.com/v8/v8/+/66178c8f53a0b8b39ead5b52d95a7ca27fbdcf81

[adamk, 2017-01-10 21:45:49]

The CQ bit was checked by adamk@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-01-10 21:45:55]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-10 22:07:03]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-01-10 22:07:04]

Dry run: Try jobs failed on following builders:
  v8_linux64_avx2_rel_ng on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux64_avx2_rel_ng/buil...)
  v8_linux64_avx2_rel_ng_triggered on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux64_avx2_rel_ng_trig...)

[adamk, 2017-01-10 22:10:53]

The CQ bit was checked by adamk@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-01-10 22:11:03]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-10 22:37:47]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-01-10 22:37:48]

Dry run: This issue passed the CQ dry run.

[Dan Ehrenberg, 2017-01-10 23:20:49]

lgtm

Do we want to keep doing these file renames for tests? What if we just left the
tests in the 'harmony' directory?

Anyway, this flag remove LGTM

[gsathya, 2017-01-10 23:22:34]

On 2017/01/10 23:20:49, Dan Ehrenberg wrote:
> lgtm
> 
> Do we want to keep doing these file renames for tests? What if we just left
the
> tests in the 'harmony' directory?
> 
> Anyway, this flag remove LGTM

I don't mind the new folder, but can we name the folder es2017?

[adamk, 2017-01-10 23:24:22]

On 2017/01/10 23:22:34, gsathya wrote:
> On 2017/01/10 23:20:49, Dan Ehrenberg wrote:
> > lgtm
> > 
> > Do we want to keep doing these file renames for tests? What if we just left
> the
> > tests in the 'harmony' directory?

I'm just following tradition at this point (and I don't think it makes sense to
leave them in "harmony").

> > Anyway, this flag remove LGTM
> 
> I don't mind the new folder, but can we name the folder es2017?

I guess so, but we already have an es7 directory as well.

[adamk, 2017-01-10 23:24:36]

The CQ bit was checked by adamk@chromium.org

[commit-bot: I haz the power, 2017-01-10 23:24:48]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-10 23:27:03]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1484090676430520,
"parent_rev": "aa0cb2eaf830e03fced1e00134fb65938df02388", "commit_rev":
"66178c8f53a0b8b39ead5b52d95a7ca27fbdcf81"}

[commit-bot: I haz the power, 2017-01-10 23:27:08]

Description was changed from

==========
Remove --harmony-async-await runtime flag

It shipped with Chrome 55 stable.

R=littledan@chromium.org
==========

to

==========
Remove --harmony-async-await runtime flag

It shipped with Chrome 55 stable.

R=littledan@chromium.org

Review-Url: https://codereview.chromium.org/2621173002
Cr-Commit-Position: refs/heads/master@{#42203}
Committed:
https://chromium.googlesource.com/v8/v8/+/66178c8f53a0b8b39ead5b52d95a7ca27fb...
==========

[commit-bot: I haz the power, 2017-01-10 23:27:10]

Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/v8/v8/+/66178c8f53a0b8b39ead5b52d95a7ca27fb...