Re: Virtualenv tests still nort running...

[Willem Jan Withagen <wjw@digiware.nl>]

On 31-3-2016 13:14, Loic Dachary wrote:
> [re-adding ceph-devel]
> 
> On 31/03/2016 12:35, Willem Jan Withagen wrote:
>> On 31-3-2016 12:14, Loic Dachary wrote:
>>> : ${CEPH_DISK_VIRTUALENV:=/tmp/ceph-disk-virtualenv}
>>
>> That works when I run it like:
>>  > cd src
>>  > ./ceph-disk/run-tox.sh
>>
>> -----------------------------------------------------
>> TOTAL                    2302   1066    54%
>> ___________________________________ summary
>> ____________________________________
>>   flake8: commands succeeded
>>   py27: commands succeeded
>>   congratulations :)
>>
>> Still leaves remainder in /tmp so that needs to be added.
>> And it will require a large enough temp with plenty freespace
> 
> It's only used for python virtualenv which is small.
> 
>> On a more philosophical note:
>> The next thing to consider is that there is a fair chance that somebody
>> mounted a tmpfs ram-disk on tmp. Which is again a different fs-beast
>> from xfs, with different properties.
> 
> This location is only used to store virutalenv, not to run actual tests.

Oke, good, because otherwise it would give room for strange results i guess.

>> Personally I do not really like the fact that the Ceph tests leave files
>> lingering just about everyware: in .src, in /tmp.
>> testdir is a real nice place to drop test things in.
>>
>> Also the fact that gtest with EXPECT_DEATH do not cleanup the *cores
>> after them is also something that would warrant some cleanup.
> 
> Yes. I expect we'll get something saner when we switch to cmake.

Oke, thanx for the pointer.
And I'll not bother hacking too much on this in the mean time.

--WjW