Re: [CMake] add_test WORKING_DIRECTORY option
On Mon, Mar 14, 2011 at 6:54 PM, Belcourt, Kenneth kbe...@sandia.gov wrote: On Mar 14, 2011, at 4:19 PM, Belcourt, Kenneth wrote: Hi David, Oops, busted. The modules I loaded inserted an older version of CMake, v2.8.1. When I run with my local copy of CMake 2.8.4, the error goes away. Sorry about the noise. -- Noel Whew. You had me going there... ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] add_test WORKING_DIRECTORY option
Hi,
The documentation states that the add_test() WORKING_DIRECTORY option
will run the test in the given directory. This add_test rule in my
CMakeLists.txt file:
add_test(
NAME bwr_melgen
WORKING_DIRECTORY ${Bwr_Dir}
COMMAND melgen.x ${Bwr_Dir}/_BWR_v2-0.inp
)
with ${Bwr_Dir} == /scratch/trunk_tests/_ShorterRuns/Plant_Decks/BWR
results in this command line.
1: Test command: /scratch/trunk/tools/melgen.x /scratch/trunk_tests/
_ShorterRuns/Plant_Decks/BWR/_BWR_v2-0.inp
Test #1: bwr_melgen
Due to problems in the code base, the output is not generated in the
test directory and this is a known code problem.
Is there an easy way to change the WORKING_DIRECTORY behavior to have
it always cd to the working directory beforehand, then run the test,
(pushd / popd behavior) etc..., rather than making, in our case the
unsafe assumption, that the program correctly writes the files where
they should be? Frankly, if ctest would always cd into the test
directory, then we'd never have a problem though we would never
uncover the incorrect file handling behavior either.
Anyone know of a way to change the working directory behavior?
-- Noel
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] add_test WORKING_DIRECTORY option
What is the cwd when your test starts?
It should be ${Bwr_Dir} according to your email's WORKING_DIRECTORY arg.
(write a little code that prints it out right at the top of the
program's main before doing anything else...)
What version of ctest is this? (I assume 2.8.4?)
always cd to the working directory beforehand, then run the test, (pushd /
popd behavior) etc...
It sets the WorkingDirectory in the process execution data structures
before launching the process. How this translates into process
launching behavior varies from platform to platform, but it should be
working essentially the same way as what you suggest.
Perhaps: are you also setting the WORKING_DIRECTORY test property? Is
that being set to a different value?
On Mon, Mar 14, 2011 at 5:19 PM, Belcourt, Kenneth kbe...@sandia.gov wrote:
Hi,
The documentation states that the add_test() WORKING_DIRECTORY option will
run the test in the given directory. This add_test rule in my
CMakeLists.txt file:
add_test(
NAME bwr_melgen
WORKING_DIRECTORY ${Bwr_Dir}
COMMAND melgen.x ${Bwr_Dir}/_BWR_v2-0.inp
)
with ${Bwr_Dir} == /scratch/trunk_tests/_ShorterRuns/Plant_Decks/BWR
results in this command line.
1: Test command: /scratch/trunk/tools/melgen.x
/scratch/trunk_tests/_ShorterRuns/Plant_Decks/BWR/_BWR_v2-0.inp
Test #1: bwr_melgen
Due to problems in the code base, the output is not generated in the test
directory and this is a known code problem.
Is there an easy way to change the WORKING_DIRECTORY behavior to have it
always cd to the working directory beforehand, then run the test, (pushd /
popd behavior) etc..., rather than making, in our case the unsafe
assumption, that the program correctly writes the files where they should
be? Frankly, if ctest would always cd into the test directory, then we'd
never have a problem though we would never uncover the incorrect file
handling behavior either.
Anyone know of a way to change the working directory behavior?
-- Noel
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] add_test WORKING_DIRECTORY option
Hi David,
On Mar 14, 2011, at 3:34 PM, David Cole wrote:
What is the cwd when your test starts?
The directory where the executable runs from (/scratch/trunk/tools),
not the directory containing the test input.
It should be ${Bwr_Dir} according to your email's WORKING_DIRECTORY
arg.
(write a little code that prints it out right at the top of the
program's main before doing anything else...)
I've confirmed with a getcwd() call at the top of the program.
What version of ctest is this? (I assume 2.8.4?)
Yes.
always cd to the working directory beforehand, then run the test,
(pushd /
popd behavior) etc...
It sets the WorkingDirectory in the process execution data structures
before launching the process. How this translates into process
launching behavior varies from platform to platform, but it should be
working essentially the same way as what you suggest.
No, doesn't seem to be.
Perhaps: are you also setting the WORKING_DIRECTORY test property? Is
that being set to a different value?
Don't think so, here's what CMake is writing to the CTestTestfile.cmake
ADD_TEST(bwr_melgen /scratch/trunk/tools/melgen.x /scratch/
trunk_tests/_ShorterRuns/Plant Decks/BWR/_BWR_v2-0.inp)
SET_TESTS_PROPERTIES(bwr_melgen PROPERTIES WORKING_DIRECTORY /
scratch/trunk_tests/_ShorterRuns/Plant Decks/BWR)
-- Noel
Here's the expected output when I cd to the input test directory and
run the executable.
[kbelco@wsblade001 BWR]$ /scratch/trunk/tools/melgen.x _BWR_v2-0.inp
cwd = /scratch/trunk_tests/_ShorterRuns/Plant Decks/BWR
Here's what I get when I run ctest.
[kbelco@wsblade001 tools]$ ctest --verbose
UpdateCTestConfiguration from :/scratch/trunk/tools/
DartConfiguration.tcl
UpdateCTestConfiguration from :/scratch/trunk/tools/
DartConfiguration.tcl
Test project /scratch/trunk/tools
Constructing a list of tests
Done constructing a list of tests
Checking test dependency graph...
test 1
Start 1: bwr_melgen
1: Test command: /scratch/trunk/tools/melgen.x /scratch/trunk_tests/
_ShorterRuns/Plant\ Decks/BWR/_BWR_v2-0.inp
1: Test timeout computed to be: 9.99988e+06
1: cwd = /scratch/trunk/tools
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] add_test WORKING_DIRECTORY option
On Mar 14, 2011, at 4:19 PM, Belcourt, Kenneth wrote: Hi David, Oops, busted. The modules I loaded inserted an older version of CMake, v2.8.1. When I run with my local copy of CMake 2.8.4, the error goes away. Sorry about the noise. -- Noel ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
