[
https://issues.apache.org/jira/browse/GEODE-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-7959:
-----------------------------
Description:
Upgrading to Mockito 3.x seems to have trouble with tests using
ConcurrentTestRunner. The result is many threads stuck trying to capture thread
stacks in invocation of mock methods.
Review of code in ConcurrentTestRunner and LoopRunner shows reveals some issues
we should improve:
* LoopRunner.execute has a hot busy while loop
* the inner for-loop of LoopRunner.runTestMethod eats exceptions without
reporting them
was:
Upgrading to Mockito 3.x seems to have trouble with tests using
ConcurrentTestRunner. The result is many threads trying to capture thread
stacks in invocation of mock methods.
Review of code in ConcurrentTestRunner and LoopRunner shows reveals some issues
we should improve:
* LoopRunner.execute has a hot busy while loop
* the inner for-loop of LoopRunner.runTestMethod eats exceptions without
reporting them
> Improve ConcurrentTestRunner in heavily loaded environment
> ----------------------------------------------------------
>
> Key: GEODE-7959
> URL: https://issues.apache.org/jira/browse/GEODE-7959
> Project: Geode
> Issue Type: Improvement
> Components: tests
> Reporter: Kirk Lund
> Assignee: Kirk Lund
> Priority: Major
>
> Upgrading to Mockito 3.x seems to have trouble with tests using
> ConcurrentTestRunner. The result is many threads stuck trying to capture
> thread stacks in invocation of mock methods.
> Review of code in ConcurrentTestRunner and LoopRunner shows reveals some
> issues we should improve:
> * LoopRunner.execute has a hot busy while loop
> * the inner for-loop of LoopRunner.runTestMethod eats exceptions without
> reporting them
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
