Test262-es6 test runner should handle sloppy fail better

Test262-es6 test runner should handle sloppy fail better

This adds a new FAIL_SLOPPY expected output. It then uses this to
determine if the test case has unexpected output.

BUG=v8:4164
LOG=N
R=machenbach@chromium.org

Committed: https://crrev.com/9f550240b03f2894ec97d6b304d1445916b9b26c
Cr-Commit-Position: refs/heads/master@{#29194}

[arv (Not doing code reviews), 2015-06-19 21:23:34]

PTAL

Is this too hacky?

If not I'll update more of the status file in follow up CLs.

[Michael Achenbach, 2015-06-22 07:03:43]

LGTM. This degree of hackiness is ok, since it is rather local to test262-es6.

[Jakob Kummerow, 2015-06-22 08:12:31]

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

[Jakob Kummerow, 2015-06-22 08:12:31]

ACK.

https://codereview.chromium.org/1197913002/diff/1/test/test262-es6/testcfg.py
File test/test262-es6/testcfg.py (right):

https://codereview.chromium.org/1197913002/diff/1/test/test262-es6/testcfg.py...
test/test262-es6/testcfg.py:142: if (statusfile.FAIL_SLOPPY in testcase.outcomes
and "--use-strict" not in testcase.flags):
nit: 80col

[arv (Not doing code reviews), 2015-06-22 14:44:24]

The CQ bit was checked by arv@chromium.org

[arv (Not doing code reviews), 2015-06-22 14:44:25]

The patchset sent to the CQ was uploaded after l-g-t-m from
machenbach@chromium.org
Link to the patchset: https://codereview.chromium.org/1197913002/#ps20001
(title: "Fix long line")

[commit-bot: I haz the power, 2015-06-22 14:44:37]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1197913002/20001

[commit-bot: I haz the power, 2015-06-22 15:08:39]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-06-22 15:09:00]

Patchset 2 (id:??) landed as
https://crrev.com/9f550240b03f2894ec97d6b304d1445916b9b26c
Cr-Commit-Position: refs/heads/master@{#29194}