ValueSerializer: Promote scheduled exceptions from wasm::ErrorThrower.

ValueSerializer: Promote scheduled exceptions from wasm::ErrorThrower.

wasm::ErrorThrower doesn't actually throw exceptions, it just schedules them.
As a result, this exception isn't handled properly by code which expects
ValueDeserializer to actually throw. For instance, the unit tests use a
TryCatch to catch and handle expected exceptions in unit tests.

Before this patch, I see local unit test failures because a wasm decode test
schedules one, but it isn't caught (and instead causes Context::New to fail
at the beginning of the next test).

BUG=685713
Review-Url: https://codereview.chromium.org/2659483004
Cr-Commit-Position: refs/heads/master@{#42718}
Committed: https://chromium.googlesource.com/v8/v8/+/78c0be52d2d8e608a15b3a9a9192ad6a9ffaf6a7

[jbroman, 2017-01-26 16:12:19]

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

[commit-bot: I haz the power, 2017-01-26 16:12:30]

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, 2017-01-26 16:43:57]

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

[commit-bot: I haz the power, 2017-01-26 16:43:58]

Dry run: This issue passed the CQ dry run.

[jbroman, 2017-01-26 18:48:10]

Description was changed from

==========
ValueSerializer: Promote scheduled exceptions from wasm::ErrorThrower.

wasm::ErrorThrower doesn't actually throw exceptions, it just schedules them.
As a result, this exception isn't handled properly by code which expects
ValueDeserializer to actually throw. For instance, the unit tests use a
TryCatch to catch and handle expected exceptions in unit tests.

Before this patch, I see local unit test failures because a wasm decode test
schedules one, but it isn't caught (and instead causes Context::New to fail
at the beginning of the next test).
==========

to

==========
ValueSerializer: Promote scheduled exceptions from wasm::ErrorThrower.

wasm::ErrorThrower doesn't actually throw exceptions, it just schedules them.
As a result, this exception isn't handled properly by code which expects
ValueDeserializer to actually throw. For instance, the unit tests use a
TryCatch to catch and handle expected exceptions in unit tests.

Before this patch, I see local unit test failures because a wasm decode test
schedules one, but it isn't caught (and instead causes Context::New to fail
at the beginning of the next test).

BUG=685713
==========

[jbroman, 2017-01-26 19:49:25]

jbroman@chromium.org changed reviewers:
+ mtrofin@chromium.org

[Mircea Trofin, 2017-01-26 19:56:19]

lgtm

[jbroman, 2017-01-26 22:16:27]

The CQ bit was checked by jbroman@chromium.org

[commit-bot: I haz the power, 2017-01-26 22:16:32]

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, 2017-01-26 22:18:29]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1485468987228290, "parent_rev":
"e6d13999fd1bdb7ca403e157e6cafd05ce4def26", "commit_rev":
"78c0be52d2d8e608a15b3a9a9192ad6a9ffaf6a7"}

[commit-bot: I haz the power, 2017-01-26 22:18:35]

Description was changed from

==========
ValueSerializer: Promote scheduled exceptions from wasm::ErrorThrower.

wasm::ErrorThrower doesn't actually throw exceptions, it just schedules them.
As a result, this exception isn't handled properly by code which expects
ValueDeserializer to actually throw. For instance, the unit tests use a
TryCatch to catch and handle expected exceptions in unit tests.

Before this patch, I see local unit test failures because a wasm decode test
schedules one, but it isn't caught (and instead causes Context::New to fail
at the beginning of the next test).

BUG=685713
==========

to

==========
ValueSerializer: Promote scheduled exceptions from wasm::ErrorThrower.

wasm::ErrorThrower doesn't actually throw exceptions, it just schedules them.
As a result, this exception isn't handled properly by code which expects
ValueDeserializer to actually throw. For instance, the unit tests use a
TryCatch to catch and handle expected exceptions in unit tests.

Before this patch, I see local unit test failures because a wasm decode test
schedules one, but it isn't caught (and instead causes Context::New to fail
at the beginning of the next test).

BUG=685713

Review-Url: https://codereview.chromium.org/2659483004
Cr-Commit-Position: refs/heads/master@{#42718}
Committed:
https://chromium.googlesource.com/v8/v8/+/78c0be52d2d8e608a15b3a9a9192ad6a9ff...
==========

[commit-bot: I haz the power, 2017-01-26 22:18:36]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/v8/v8/+/78c0be52d2d8e608a15b3a9a9192ad6a9ff...