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

• Type: Test
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.15.0
• Component/s: tests
• Labels: pull-request-available
• Assignee: Dale Emery
• Reporter: Dale Emery
• Created: 11/May/21 19:07
• Updated: 11/May/21 22:13
• Resolved: 11/May/21 22:13

Description

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.

Issue Links

• links to: GitHub Pull Request #6463