Make testharness.js tests fail on uncaught exceptions

Make testharness.js tests fail on uncaught exceptions

If a LayoutTest throws an uncaught exception before the
testharness.js script has loaded the exception is ignored
and the test may still pass.

This patch updates the LayoutTests runner to see uncaught exceptions
in testharness.js tests as test failure.

Tests that are legitimately testing uncaught exceptions now have
explicit expectations for these errors.

BUG=602886

[alancutter (OOO until 2018), 2016-04-13 01:46:58]

Description was changed from

==========
lint


+failOnUncaughtError

BUG=
==========

to

==========
Make testharness.js tests fail on uncaught exceptions

This patch updates the LayoutTests runner to see uncaught exceptions
in testharness.js tests as test failure.
Previously these errors were ignored and the test would pass if no
inner tests failed.

BUG=602886
==========

[alancutter (OOO until 2018), 2016-04-13 01:46:58]

alancutter@chromium.org changed reviewers:
+ tansell@chromium.org

[alancutter (OOO until 2018), 2016-04-13 01:49:31]

Description was changed from

==========
Make testharness.js tests fail on uncaught exceptions

This patch updates the LayoutTests runner to see uncaught exceptions
in testharness.js tests as test failure.
Previously these errors were ignored and the test would pass if no
inner tests failed.

BUG=602886
==========

to

==========
Make testharness.js tests fail on uncaught exceptions

If a LayoutTest throws an uncaught exception before the
testharness.js script has loaded the exception is ignored
and the test may still pass.

This patch updates the LayoutTests runner to see uncaught exceptions
in testharness.js tests as test failure.

BUG=602886
==========

[alancutter (OOO until 2018), 2016-04-13 01:52:56]

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

[commit-bot: I haz the power, 2016-04-13 01:53:17]

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

[commit-bot: I haz the power, 2016-04-13 03:05:57]

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

[commit-bot: I haz the power, 2016-04-13 03:05:58]

Dry run: Try jobs failed on following builders:
  linux_chromium_rel_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[alancutter (OOO until 2018), 2016-04-13 03:57:30]

On 2016/04/13 at 03:05:58, commit-bot wrote:
> Dry run: Try jobs failed on following builders:
>   linux_chromium_rel_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

Looks like there are a ton of new expectation files to create and a handful of
buggy LayoutTests to fix up.

[alancutter (OOO until 2018), 2016-04-13 07:43:26]

Description was changed from

==========
Make testharness.js tests fail on uncaught exceptions

If a LayoutTest throws an uncaught exception before the
testharness.js script has loaded the exception is ignored
and the test may still pass.

This patch updates the LayoutTests runner to see uncaught exceptions
in testharness.js tests as test failure.

BUG=602886
==========

to

==========
Make testharness.js tests fail on uncaught exceptions

If a LayoutTest throws an uncaught exception before the
testharness.js script has loaded the exception is ignored
and the test may still pass.

This patch updates the LayoutTests runner to see uncaught exceptions
in testharness.js tests as test failure.

Tests that are legitimately testing uncaught exceptions now have
explicit expectations for these errors.

BUG=602886
==========

[alancutter (OOO until 2018), 2016-04-13 07:48:04]

alancutter@chromium.org changed reviewers:
+ dpranke@chromium.org
- tansell@chromium.org

[alancutter (OOO until 2018), 2016-04-13 07:48:05]

Changing reviewer to dpranke.
Please let me know if there are any issues with this new approach to
testharness.js failures.

[alancutter (OOO until 2018), 2016-04-13 07:48:22]

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

[commit-bot: I haz the power, 2016-04-13 07:48:45]

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

[commit-bot: I haz the power, 2016-04-13 08:36:31]

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

[commit-bot: I haz the power, 2016-04-13 08:36:33]

Dry run: Try jobs failed on following builders:
  win_chromium_rel_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[alancutter (OOO until 2018), 2016-04-14 08:29:47]

On 2016/04/13 at 08:36:33, commit-bot wrote:
> Dry run: Try jobs failed on following builders:
>   win_chromium_rel_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

Hmm, some of these tests output random nonces, a bit hard to add expectations
for...