[jira] [Updated] (MESOS-4806) LeveDBStateTests write to the current directory

["Benjamin Bannier (JIRA)" <ji...@apache.org>]

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

Benjamin Bannier updated MESOS-4806:
------------------------------------
         Labels: newbie parallel-tests  (was: )
    Description: 
All {{LevelDBStateTest}} tests write to the current directory. This is bad for a number of reasons, e.g.,

* should the test fail data might be leaked to random locations,
* the test cannot be executed from a write-only directory, or
* executing tests from the same suite in parallel (e.g., with {{gtest-parallel}} would race on the existence of the created files, and show bogus behavior.

The tests should probably be executed from a temporary directory, e.g., via stout's {{TemporaryDirectoryTest}} fixture.

> LeveDBStateTests write to the current directory
> -----------------------------------------------
>
>                 Key: MESOS-4806
>                 URL: https://issues.apache.org/jira/browse/MESOS-4806
>             Project: Mesos
>          Issue Type: Bug
>          Components: test, tests
>            Reporter: Benjamin Bannier
>              Labels: newbie, parallel-tests
>
> All {{LevelDBStateTest}} tests write to the current directory. This is bad for a number of reasons, e.g.,
> * should the test fail data might be leaked to random locations,
> * the test cannot be executed from a write-only directory, or
> * executing tests from the same suite in parallel (e.g., with {{gtest-parallel}} would race on the existence of the created files, and show bogus behavior.
> The tests should probably be executed from a temporary directory, e.g., via stout's {{TemporaryDirectoryTest}} fixture.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)