ctest with some flags creates Testing directory + artifacts
When ctest
is run with the -j
flag (for specifying number of parallel jobs), if the directory is not a build directory, it will leave a Testing
folder around. When ctest
does not have -j
specified, a different output is written and the Testing
directory is not created.
To reproduce:
[ascheel@ascheel-t450s ~]$ mkdir /tmp/ctest-example && cd /tmp/ctest-example
[ascheel@ascheel-t450s ctest-example]$ ctest
*********************************
No test configuration file found!
*********************************
Usage
ctest [options]
[ascheel@ascheel-t450s ctest-example]$ ls -l
total 0
[ascheel@ascheel-t450s ctest-example]$ ctest -j4
Test project /tmp/ctest-example
No tests were found!!!
[ascheel@ascheel-t450s ctest-example]$ ls -l
total 0
drwxr-xr-x. 3 ascheel ascheel 60 Jul 6 09:42 Testing
[ascheel@ascheel-t450s ctest-example]$ find
.
./Testing
./Testing/Temporary
./Testing/Temporary/LastTest.log
./Testing/Temporary/CTestCostData.txt
[ascheel@ascheel-t450s ctest-example]$ ctest --version
ctest version 3.11.2
CMake suite maintained and supported by Kitware (kitware.com/cmake).
Thanks!