[
https://issues.apache.org/jira/browse/GEODE-9260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342895#comment-17342895
]
ASF subversion and git services commented on GEODE-9260:
--------------------------------------------------------
Commit 1d4d507e8af2ffb53249c10316123774973c39f7 in geode's branch
refs/heads/develop from Dale Emery
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1d4d507 ]
GEODE-9260: One test class per JVM in repeat tests (#6463)
Repeat test tasks are now configured to `forkEvery 1` in order to run
each test class in a fresh test worker JVM. Many of the tests run by
these tasks leave the JVM in a state that other test classes cannot
tolerate.
Authored-by: Dale Emery <[email protected]>
> 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
> Priority: Major
> Labels: pull-request-available
>
> 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)
