Clear unhandled scheduled exceptions from ValueSelializerTest

[test] Clear unhandled scheduled exceptions from ValueSerializerTest

This patch adds destructor to ValueSerializerTest test fixture class
which reset unhandled scheduled exceptions thrown from the current test.
In some cases unhandled scheduled exceptions from current test (eg.
from one test from ValueSerializerTestWithWasm test case) produce that
Context::New(isolate()) from next test's constructor returns NULL.

This error is easily reproduced when unittest file (compiled for ARM or
MIPS simulator) is directly executed (not by tools/run_tests.py script),
so all tests are executed together. When the script is used, each test
from ValueSerializerTestWithWasm test case is separately executed and
unhandled exception from one test doesn't efect to another test from
the same test case.

BUG=

Review-Url: https://codereview.chromium.org/2644083002
Cr-Commit-Position: refs/heads/master@{#42547}
Committed: https://chromium.googlesource.com/v8/v8/+/73281702c8ae1fe22c2c718bc0f5dd4af66abfb4

[dusan.simicic, 2017-01-19 11:04:09]

dusan.simicic@imgtec.com changed reviewers:
+ ivica.bogosavljevic@imgtec.com, miran.karic@imgtec.com,
v8-mips-ports@googlegroups.com

[dusan.simicic, 2017-01-19 11:04:09]

PTAL

[Jakob Kummerow, 2017-01-19 15:08:17]

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

[Jakob Kummerow, 2017-01-19 15:08:18]

lgtm

[Jakob Kummerow, 2017-01-19 15:08:36]

Description was changed from

==========
Clear unhandled scheduled exceptions from ValueSelializerTest

This patch adds destructor to ValueSerializerTest test fixture class
which reset unhandled scheduled exceptions thrown from the current test.
In some cases unhandled scheduled exceptions from current test (eg.
from one test from ValueSerializerTestWithWasm test case) produce that
Context::New(isolate()) from next test's constructor returns NULL.

This error is easily reproduced when unittest file (compiled for ARM or
MIPS simulator) is directly executed (not by tools/run_tests.py script),
so all tests are executed together. When the script is used, each test
from ValueSerializerTestWithWasm test case is separately executed and
unhandled exception from one test doesn't efect to another test from
the same test case.

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

to

==========
[test] Clear unhandled scheduled exceptions from ValueSerializerTest

This patch adds destructor to ValueSerializerTest test fixture class
which reset unhandled scheduled exceptions thrown from the current test.
In some cases unhandled scheduled exceptions from current test (eg.
from one test from ValueSerializerTestWithWasm test case) produce that
Context::New(isolate()) from next test's constructor returns NULL.

This error is easily reproduced when unittest file (compiled for ARM or
MIPS simulator) is directly executed (not by tools/run_tests.py script),
so all tests are executed together. When the script is used, each test
from ValueSerializerTestWithWasm test case is separately executed and
unhandled exception from one test doesn't efect to another test from
the same test case.

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

[dusan.simicic, 2017-01-20 09:29:10]

The CQ bit was checked by dusan.simicic@imgtec.com to run a CQ dry run

[commit-bot: I haz the power, 2017-01-20 09:29:21]

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-20 10:02:36]

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

[commit-bot: I haz the power, 2017-01-20 10:02:37]

Dry run: This issue passed the CQ dry run.

[dusan.simicic, 2017-01-20 10:13:27]

The CQ bit was unchecked by dusan.simicic@imgtec.com

[dusan.simicic, 2017-01-20 10:13:29]

The CQ bit was checked by dusan.simicic@imgtec.com

[commit-bot: I haz the power, 2017-01-20 10:13:37]

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-20 10:49:06]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1484907209021760, "parent_rev":
"7425b1f2c9c026dd6e4f7471995d4d605262d553", "commit_rev":
"73281702c8ae1fe22c2c718bc0f5dd4af66abfb4"}

[commit-bot: I haz the power, 2017-01-20 10:49:10]

Description was changed from

==========
[test] Clear unhandled scheduled exceptions from ValueSerializerTest

This patch adds destructor to ValueSerializerTest test fixture class
which reset unhandled scheduled exceptions thrown from the current test.
In some cases unhandled scheduled exceptions from current test (eg.
from one test from ValueSerializerTestWithWasm test case) produce that
Context::New(isolate()) from next test's constructor returns NULL.

This error is easily reproduced when unittest file (compiled for ARM or
MIPS simulator) is directly executed (not by tools/run_tests.py script),
so all tests are executed together. When the script is used, each test
from ValueSerializerTestWithWasm test case is separately executed and
unhandled exception from one test doesn't efect to another test from
the same test case.

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

to

==========
[test] Clear unhandled scheduled exceptions from ValueSerializerTest

This patch adds destructor to ValueSerializerTest test fixture class
which reset unhandled scheduled exceptions thrown from the current test.
In some cases unhandled scheduled exceptions from current test (eg.
from one test from ValueSerializerTestWithWasm test case) produce that
Context::New(isolate()) from next test's constructor returns NULL.

This error is easily reproduced when unittest file (compiled for ARM or
MIPS simulator) is directly executed (not by tools/run_tests.py script),
so all tests are executed together. When the script is used, each test
from ValueSerializerTestWithWasm test case is separately executed and
unhandled exception from one test doesn't efect to another test from
the same test case.

BUG=

Review-Url: https://codereview.chromium.org/2644083002
Cr-Commit-Position: refs/heads/master@{#42547}
Committed:
https://chromium.googlesource.com/v8/v8/+/73281702c8ae1fe22c2c718bc0f5dd4af66...
==========

[commit-bot: I haz the power, 2017-01-20 10:49:10]

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