Update webkit test expectations for sloppy functions in case

Update webkit test expectations for sloppy functions in case

A recent ES2015 semantics web compatibility fix changed a WebKit
test from a syntax error to a known failure without a syntax
error. This confused the fuzzer infrastructure. This patch updates
the test expectations to the expected output, based on what the
new semantics provide.

R=machenbach,adamk
BUG=v8:4693
LOG=N

Committed: https://crrev.com/5ef27c25e9cbc9d78abd580c3c8b7f121db69fc5
Cr-Commit-Position: refs/heads/master@{#33484}

[Dan Ehrenberg, 2016-01-25 08:45:48]

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

[commit-bot: I haz the power, 2016-01-25 08:45:55]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1628013003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1628013003/1

[Michael Achenbach, 2016-01-25 08:47:52]

machenbach@chromium.org changed reviewers:
+ machenbach@chromium.org

[Michael Achenbach, 2016-01-25 08:47:53]

lgtm

https://codereview.chromium.org/1628013003/diff/1/test/webkit/function-declar...
File test/webkit/function-declarations-in-switch-statement-expected.txt (right):

https://codereview.chromium.org/1628013003/diff/1/test/webkit/function-declar...
test/webkit/function-declarations-in-switch-statement-expected.txt:29: FAIL -1
should be 20. Was -1.
Maybe changing the .js file would look cleaner if the new semantics are correct.

[Dan Ehrenberg, 2016-01-25 08:52:20]

https://codereview.chromium.org/1628013003/diff/1/test/webkit/function-declar...
File test/webkit/function-declarations-in-switch-statement-expected.txt (right):

https://codereview.chromium.org/1628013003/diff/1/test/webkit/function-declar...
test/webkit/function-declarations-in-switch-statement-expected.txt:29: FAIL -1
should be 20. Was -1.
On 2016/01/25 at 08:47:52, Michael Achenbach wrote:
> Maybe changing the .js file would look cleaner if the new semantics are
correct.

In some cases, it seems like we've been avoiding changing these webkit tests, as
they're largely historical. Also, it's possible that in the future we'll want to
restore the syntax error behavior (pending TC39)--its still unclear what
semantics we want. That's why I decided to make this a change in expectations,
not the test itself.

[Dan Ehrenberg, 2016-01-25 08:52:23]

The CQ bit was unchecked by littledan@chromium.org

[Dan Ehrenberg, 2016-01-25 08:52:25]

The CQ bit was checked by littledan@chromium.org

[commit-bot: I haz the power, 2016-01-25 08:52:35]

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

[commit-bot: I haz the power, 2016-01-25 09:02:38]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-01-25 09:03:02]

Description was changed from

==========
Update webkit test expectations for sloppy functions in case

A recent ES2015 semantics web compatibility fix changed a WebKit
test from a syntax error to a known failure without a syntax
error. This confused the fuzzer infrastructure. This patch updates
the test expectations to the expected output, based on what the
new semantics provide.

R=machenbach,adamk
BUG=v8:4693
LOG=N
==========

to

==========
Update webkit test expectations for sloppy functions in case

A recent ES2015 semantics web compatibility fix changed a WebKit
test from a syntax error to a known failure without a syntax
error. This confused the fuzzer infrastructure. This patch updates
the test expectations to the expected output, based on what the
new semantics provide.

R=machenbach,adamk
BUG=v8:4693
LOG=N

Committed: https://crrev.com/5ef27c25e9cbc9d78abd580c3c8b7f121db69fc5
Cr-Commit-Position: refs/heads/master@{#33484}
==========

[commit-bot: I haz the power, 2016-01-25 09:03:03]

Patchset 1 (id:??) landed as
https://crrev.com/5ef27c25e9cbc9d78abd580c3c8b7f121db69fc5
Cr-Commit-Position: refs/heads/master@{#33484}