[GEODE-8495] Make DUnit launch members in non-conflicting directories

• Type: Test
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Component/s: tests
• Labels: GeodeOperationAPI pull-request-available
• Assignee: Dale Emery
• Reporter: Dale Emery
• Created: 14/Sep/20 23:58
• Updated: 11/Mar/21 18:15
• Resolved: 26/Oct/20 17:18

Description

Currently several features of the DUnit framework prevent tests being run in parallel outside of a docker container:

1. The DUnitLauncher launches child VMs in subdirectories with standard names (e.g. vm0, vm1, ...) in the test JVM's working directory. If multiple tests run in parallel, the child VMs created by each test share these directories.

2. LocatorStarterRule and ServerStarterRule launch locators and servers in the test JVM, directly in the test JVM's working directory. If multiple tests run in parallel, the members started by these rules share these directories.

Each member expects to be the only thing running in its working directory. When members from different tests share directories, they become confused and fail.

To allow running tests in parallel outside of docker containers, fix these and other directory conflict problems.

Issue Links

• is superceded by: GEODE-8637 Configure Gradle to run each test worker in a unique working directory
• links to: GitHub Pull Request #5586