[
https://issues.apache.org/jira/browse/GEODE-8495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206295#comment-17206295
]
ASF GitHub Bot commented on GEODE-8495:
---------------------------------------
demery-pivotal merged pull request #5586:
URL: https://github.com/apache/geode/pull/5586
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Make DUnit launch members in non-conflicting directories [PERMANENT]
> --------------------------------------------------------------------
>
> Key: GEODE-8495
> URL: https://issues.apache.org/jira/browse/GEODE-8495
> Project: Geode
> Issue Type: Test
> Components: tests
> Reporter: Dale Emery
> Assignee: Dale Emery
> Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
