You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dan Smith (JIRA)" <ji...@apache.org> on 2016/05/10 21:24:13 UTC
[jira] [Created] (GEODE-1378) checkMissedTests launches dunit VMs,
takes time
Dan Smith created GEODE-1378:
--------------------------------
Summary: checkMissedTests launches dunit VMs, takes time
Key: GEODE-1378
URL: https://issues.apache.org/jira/browse/GEODE-1378
Project: Geode
Issue Type: Bug
Components: build, tests
Reporter: Dan Smith
The checkMissedTests target actually triggers the launch of dunit VMs, even though no tests are run (normally).
I think this has to do with how the dunit framework is written and how we are using categories.
For junit 4 tests, we are launching the dunit framework from a BeforeClass in JUnit4DistributedTest method. For unit 3 tests, we launch the dunit framework from with the constructor of Junt3DistributedTests.
I think junit is calling one of these things (probably the junit 3 contructor) when it is determining the categories of the tests. That's causing the checkMissedTests target to launch all of the dunit VMs even though it doesn't run the tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)