[
https://issues.apache.org/jira/browse/GEODE-8495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206296#comment-17206296
]
ASF subversion and git services commented on GEODE-8495:
--------------------------------------------------------
Commit 6d58009eb7b391dfbdbe8c673af596ab4da41096 in geode's branch
refs/heads/develop from Dale Emery
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=6d58009 ]
GEODE-8495: Make tests honor default disk dir property (#5586)
The testClientSubscriptionQueueUsingDefaultDS() test in
CacheXml66DUnitTest and its subclasses assumed that the system’s default
disk directory is the JVM’s current working directory.
This change removes that assumption by making the tests honor the
defaultDiskDirs system property.
Authored-by: Dale Emery <dem...@vmware.com>
> 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)
