tree 5f89e3ba4a49bb7c6da95ddc30eae09de698ae72
parent 00d9c36630c3b100532e86e2616da21d7c5e504a
author ysuzuki@apple.com <ysuzuki@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> 1643192672 +0000
committer ysuzuki@apple.com <ysuzuki@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> 1643192672 +0000

[JSC] Do not run testPingPongStackOverflow while running multithreaded MultithreadedMultiVMExecutionTest
https://bugs.webkit.org/show_bug.cgi?id=235633

Reviewed by Mark Lam.

MultithreadedMultiVMExecutionTest is failing occasionally in CLoop test. This is because of the following.

1. CLoop is slow, so multithreaded tests are running longly.
2. Then, this multithreaded tests overlap with testPingPongStackOverflow.
3. testPingPongStackOverflow changes global Options::maxPerThreadStackUsage to test stack-overflow behavior.
   This test is strongly assuming that there is only one thread using this VM. But this is wrong since
   MultithreadedMultiVMExecutionTest is running concurrently. Then this configuration change affects on
   the running MultithreadedMultiVMExecutionTest.
4. Stack-overflow error happens in MultithreadedMultiVMExecutionTest if the changed option is observed in that test.

We should not run testPingPongStackOverflow until MultithreadedMultiVMExecutionTest finishes since it assumes
that there is only one user of this VM.

This patch also cleans up / adds diagnosis of failures in MultithreadedMultiVMExecutionTest.

* API/tests/MultithreadedMultiVMExecutionTest.cpp:
(startMultithreadedMultiVMExecutionTest):
(finalizeMultithreadedMultiVMExecutionTest):
* API/tests/testapi.c:
(main):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@288612 268f45cc-cd09-0410-ab3c-d52691b4dbfc