You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dale Emery (Jira)" <ji...@apache.org> on 2021/02/18 19:46:00 UTC

[jira] [Resolved] (GEODE-8942) Fix test worker JVM working dir name when running in docker

     [ https://issues.apache.org/jira/browse/GEODE-8942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dale Emery resolved GEODE-8942.
-------------------------------
    Fix Version/s: 1.15.0
       Resolution: Fixed

> 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
>             Fix For: 1.15.0
>
>
> 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)