[ 
https://issues.apache.org/jira/browse/GEODE-8942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285352#comment-17285352
 ] 

ASF subversion and git services commented on GEODE-8942:
--------------------------------------------------------

Commit 3a1534cdb932bcced588dc441294fee21ce57a47 in geode's branch 
refs/heads/develop from Dale Emery
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3a1534c ]

GEODE-8942: Fix docker.gradle working dir (#6030)

Change docker.gradle to stop appending the Gradle worker ID onto the
test worker JVM's working directory name. As of GEODE-8637, the working
directory is already unique by the time docker.gradle operates on it,
and appending the worker ID makes the test run in the wrong directory.

> Fix test worker JVM working dir name when running in docker
> -----------------------------------------------------------
>
>                 Key: GEODE-8942
>                 URL: https://issues.apache.org/jira/browse/GEODE-8942
>             Project: Geode
>          Issue Type: Test
>          Components: tests
>    Affects Versions: 1.13.0
>            Reporter: Dale Emery
>            Assignee: Dale Emery
>            Priority: Major
>              Labels: GeodeOperationAPI, pull-request-available
>
> GEODE-8637 changed Geode's Gradle build script to give each test worker JVM 
> its own, unique working directory, and to copy the default gemfire.properties 
> file into each working directory.
> When a test will be run in docker, docker.gradle further differentiates each 
> test worker JVM's working directory by appending the Gradle worker ID. 
> GEODE-8637 made this unnecessary, but did not edit docker.gradle to stop 
> appending the worker ID.
> As a result, running dockerized tests creates unnecessary directories, and 
> executes each test in a directory that lacks the default gemfire.properties.
> Solution: Change docker.gradle to stop appending the worker ID onto the 
> already unique working directory name.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to