Remove --harmony-arrow-functions flag

Remove --harmony-arrow-functions flag

Arrow functions have been enabled by default since the 4.5 branch.

Committed: https://crrev.com/163419e8fa20b5a6730f874ccdb092ef51739600
Cr-Commit-Position: refs/heads/master@{#31031}

[adamk, 2015-09-25 22:00:25]

Patchset #1 (id:1) has been deleted

[adamk, 2015-09-25 22:01:01]

adamk@chromium.org changed reviewers:
+ aperez@igalia.com, rossberg@chromium.org, wingo@igalia.com

[aperez, 2015-09-26 16:56:03]

On 2015/09/25 22:01:01, adamk wrote:

LGTM (non-owner review).

[aperez, 2015-09-26 17:06:28]

On 2015/09/26 16:56:03, aperez wrote:
> On 2015/09/25 22:01:01, adamk wrote:
> 
> LGTM (non-owner review).

For the record, it would be needd to figure out why some of the bots are red
while most of them are passing. There are some failures in which the expected
outcome seems to be wrong:

  Exit code: 1
  Result: FAIL
  Expected outcomes: PASS
  Duration: 00:00:063

  Stdout:
 
/b/build/slave/mac/build/v8/test/message/arrow-strict-eval-bare-parameter.js:6:
SyntaxError: Unexpected eval or arguments in strict mode
  eval => 42
  ^^^^
  SyntaxError: Unexpected eval or arguments in strict mode

For example in the case above the SyntaxError is to be expected because it's
using “eval” as a parameter in strict mode, which is forbidden by the spec. The
expected outcome of the test case shuld be FAIL.

[adamk, 2015-09-28 18:26:42]

On 2015/09/26 17:06:28, aperez wrote:
> On 2015/09/26 16:56:03, aperez wrote:
> > On 2015/09/25 22:01:01, adamk wrote:
> > 
> > LGTM (non-owner review).
> 
> For the record, it would be needd to figure out why some of the bots are red
> while most of them are passing. There are some failures in which the expected
> outcome seems to be wrong:
> 
>   Exit code: 1
>   Result: FAIL
>   Expected outcomes: PASS
>   Duration: 00:00:063
> 
>   Stdout:
>  
>
/b/build/slave/mac/build/v8/test/message/arrow-strict-eval-bare-parameter.js:6:
> SyntaxError: Unexpected eval or arguments in strict mode
>   eval => 42
>   ^^^^
>   SyntaxError: Unexpected eval or arguments in strict mode
> 
> For example in the case above the SyntaxError is to be expected because it's
> using “eval” as a parameter in strict mode, which is forbidden by the spec.
The
> expected outcome of the test case shuld be FAIL.

The latest patchset fixes these. The problem was that, because I removed the
"Flags" line from the tests, the error messages had a different line number than
before.

[adamk, 2015-09-30 00:31:44]

rossberg, ping

[rossberg, 2015-09-30 13:33:24]

lgtm

[adamk, 2015-09-30 19:23:30]

The CQ bit was checked by adamk@chromium.org

[adamk, 2015-09-30 19:23:31]

The patchset sent to the CQ was uploaded after l-g-t-m from aperez@igalia.com,
rossberg@chromium.org
Link to the patchset: https://codereview.chromium.org/1373633002/#ps80001
(title: "Rebased")

[commit-bot: I haz the power, 2015-09-30 19:23:52]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1373633002/80001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1373633002/80001

[commit-bot: I haz the power, 2015-09-30 19:49:55]

Committed patchset #4 (id:80001)

[commit-bot: I haz the power, 2015-09-30 19:50:48]

Patchset 4 (id:??) landed as
https://crrev.com/163419e8fa20b5a6730f874ccdb092ef51739600
Cr-Commit-Position: refs/heads/master@{#31031}