[CMake] CTest -D MemoryCheck hangs when not run from CMAKE_BINARY_DIR
Marcel Loose
loose at astron.nl
Mon Feb 15 05:56:16 EST 2010
Hi all,
I noticed that "ctest -D MemoryCheck" hangs when it is not run from the
top-level binary directory (CMAKE_BINARY_DIR). This is weird, in so far,
that simply running "ctest" in that directory causes no problem.
When I 'strace' the 'ctest' process I notice that it seems to 'stat'
every file on my file system, which obviously takes some time ;-).
Is this a bug?
Please see below the output of "ctest -V -D MemoryCheck" when being run
from a directory below CMAKE_BINARY_DIR. I killed the process after
approx. 1 minute. Notice that a lot of (required?) information is
missing from the DartConfiguration.tcl file.
Best regards,
Marcel Loose.
### Start of output of "ctest -V -D MemoryCheck" ###
UpdateCTestConfiguration
from
:/export/home/loose/work/LOFAR_trunk/build/gnu_debug/LCS/Common/DartConfiguration.tcl
Cannot find
file:
/export/home/loose/work/LOFAR_trunk/build/gnu_debug/LCS/Common/DartConfiguration.tcl
Site:
Build name:
Add coverage exclude regular expressions.
Create new tag: 20100215-1045 - Experimental
Start processing tests
Configure project
Cannot find ConfigureCommand key in the DartConfiguration.tcl
UpdateCTestConfiguration
from
:/export/home/loose/work/LOFAR_trunk/build/gnu_debug/LCS/Common/DartConfiguration.tcl
Cannot find
file:
/export/home/loose/work/LOFAR_trunk/build/gnu_debug/LCS/Common/DartConfiguration.tcl
Build project
MakeCommand:
Cannot find MakeCommand key in the DartConfiguration.tcl
UpdateCTestConfiguration
from
:/export/home/loose/work/LOFAR_trunk/build/gnu_debug/LCS/Common/DartConfiguration.tcl
Cannot find
file:
/export/home/loose/work/LOFAR_trunk/build/gnu_debug/LCS/Common/DartConfiguration.tcl
Performing coverage
COVFILE environment variable not found, not running bullseye
### End of output of "ctest -V -D MemoryCheck" ###
More information about the CMake
mailing list