[test] Fix exception parsing in test262.

[test] Fix exception parsing in test262.

The _ParseException function in testcfg.py made incorrect assumptions about how
exceptions are printed (I believe it expected a trace like that produced by
Error).

R=littledan@chromium.org
BUG=v8:5136
Committed: https://crrev.com/194e418614e7db30fab0f5c7c91681abb67878ee
Cr-Commit-Position: refs/heads/master@{#40078}

[neis, 2016-10-06 15:12:39]

Description was changed from

==========
[test] Fix exception parsing in test262.

The _ParseException function in testcfg.py made incorrect assumptions about how
exceptions are printed (I believe it expected a trace like that produced by
Error).

R=littledan@chromium.org
BUG=v8:5136
==========

to

==========
[test] Fix exception parsing in test262.

The _ParseException function in testcfg.py made incorrect assumptions about how
exceptions are printed (I believe it expected a trace like that produced by
Error).

R=littledan@chromium.org
BUG=v8:5136
==========

[neis, 2016-10-06 15:12:39]

neis@chromium.org changed reviewers:
+ adamk@chromium.org

[neis, 2016-10-06 15:12:53]

+adamk since Dan is away.

[adamk, 2016-10-06 18:13:18]

lgtm if the tests like it

[neis, 2016-10-07 07:59:12]

The CQ bit was checked by neis@chromium.org

[commit-bot: I haz the power, 2016-10-07 07:59:19]

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, 2016-10-07 08:16:27]

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

[commit-bot: I haz the power, 2016-10-07 08:16:27]

Try jobs failed on following builders:
  v8_linux_nodcheck_rel_ng on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_nodcheck_rel_ng/bu...)
  v8_linux_nodcheck_rel_ng_triggered on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_nodcheck_rel_ng_tr...)

[neis, 2016-10-07 09:47:07]

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

[commit-bot: I haz the power, 2016-10-07 09:47:12]

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, 2016-10-07 10:17:41]

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

[commit-bot: I haz the power, 2016-10-07 10:17:41]

Dry run: This issue passed the CQ dry run.

[neis, 2016-10-07 10:18:45]

The CQ bit was checked by neis@chromium.org

[neis, 2016-10-07 10:18:46]

The patchset sent to the CQ was uploaded after l-g-t-m from adamk@chromium.org
Link to the patchset: https://codereview.chromium.org/2386103010/#ps20001
(title: "Deal with --stress-opt output.")

[commit-bot: I haz the power, 2016-10-07 10:18: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, 2016-10-07 10:20:49]

Description was changed from

==========
[test] Fix exception parsing in test262.

The _ParseException function in testcfg.py made incorrect assumptions about how
exceptions are printed (I believe it expected a trace like that produced by
Error).

R=littledan@chromium.org
BUG=v8:5136
==========

to

==========
[test] Fix exception parsing in test262.

The _ParseException function in testcfg.py made incorrect assumptions about how
exceptions are printed (I believe it expected a trace like that produced by
Error).

R=littledan@chromium.org
BUG=v8:5136
==========

[commit-bot: I haz the power, 2016-10-07 10:20:50]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-10-07 10:21:17]

Description was changed from

==========
[test] Fix exception parsing in test262.

The _ParseException function in testcfg.py made incorrect assumptions about how
exceptions are printed (I believe it expected a trace like that produced by
Error).

R=littledan@chromium.org
BUG=v8:5136
==========

to

==========
[test] Fix exception parsing in test262.

The _ParseException function in testcfg.py made incorrect assumptions about how
exceptions are printed (I believe it expected a trace like that produced by
Error).

R=littledan@chromium.org
BUG=v8:5136

Committed: https://crrev.com/194e418614e7db30fab0f5c7c91681abb67878ee
Cr-Commit-Position: refs/heads/master@{#40078}
==========

[commit-bot: I haz the power, 2016-10-07 10:21:18]

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