[jira] [Closed] (GEODE-9260) Repeat test tasks should each test class in its own test worker JVM

["Dale Emery (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GEODE-9260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dale Emery closed GEODE-9260.
-----------------------------

> Repeat test tasks should each test class in its own test worker JVM
> -------------------------------------------------------------------
>
>                 Key: GEODE-9260
>                 URL: https://issues.apache.org/jira/browse/GEODE-9260
>             Project: Geode
>          Issue Type: Test
>          Components: tests
>            Reporter: Dale Emery
>            Assignee: Dale Emery
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.15.0
>
>
> The test classes exercised by Geode's acceptanceTest, distributedTest, integrationTest, performanceTest, uiTest, and upgradeTest tasks typically do not leave the test worker JVM in a state where other test classes can succeed. For this reason, these tasks all specify `forkEvery = 1`, giving each test class a fresh test worker JVM.
> The corresponding repeat test tasks leave `forkEvery` at the default value, which runs multiple test classes in each test worker. This produces swarms of test failures. For example, running all distributed tests via `repeatDistributedTest` produces about 1450 test failures.
> Repeat test tasks should specify `forkEvery = 1` to run each test class in a fresh test worker JVM.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)