geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Smith (JIRA)" <>
Subject [jira] [Updated] (GEODE-1378) checkMissedTests launches dunit VMs, takes time
Date Wed, 18 May 2016 18:37:12 GMT


Dan Smith updated GEODE-1378:
    Fix Version/s: 1.0.0-incubating.M3

> checkMissedTests launches dunit VMs, takes time
> -----------------------------------------------
>                 Key: GEODE-1378
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: build, tests
>            Reporter: Dan Smith
>            Assignee: Dan Smith
>             Fix For: 1.0.0-incubating.M3
> 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

View raw message