Starts the testing for a given model
ctest_start(<model> [<source> [<binary>]] [TRACK <track>] [QUIET]) ctest_start([<model> [<source> [<binary>]]] [TRACK <track>] APPEND [QUIET])
Starts the testing for a given model. The command should be called after the binary directory is initialized.
The parameters are as follows:
Nightly. This parameter is required unless
CTEST_SOURCE_DIRECTORYis used instead.
CTEST_BINARY_DIRECTORYis used instead.
TRACKis used, the submissions will go to the specified track on the CDash server. If no
TRACKis specified, the name of the model is used by default.
APPEND is used, the existing
TAG is used rather than creating a new one based on the current time stamp. If you use
APPEND, you can omit the
TRACK <track> parameters, because they will be read from the generated
TAG file. For example:
ctest_start(Experimental TRACK TrackExperimental)
Later, in another
ctest -S script:
When the second script runs
ctest_start(APPEND), it will read the
Experimental model and
TrackExperimental track from the
TAG file generated by the first
ctest_start() command. Please note that if you call
ctest_start(APPEND) and specify a different model or track than in the first
ctest_start() command, a warning will be issued, and the new model and track will be used.
QUIETis used, CTest will suppress any non-error messages that it otherwise would have printed to the console.
The parameters for
ctest_start() can be issued in any order, with the exception that
<binary> have to appear in that order with respect to each other. The following are all valid and equivalent:
ctest_start(Experimental path/to/source path/to/binary TRACK SomeTrack QUIET APPEND) ctest_start(TRACK SomeTrack Experimental QUIET path/to/source APPEND path/to/binary) ctest_start(APPEND QUIET Experimental path/to/source TRACK SomeTrack path/to/binary)
However, for the sake of readability, it is recommended that you order your parameters in the order listed at the top of this page.
CTEST_CHECKOUT_COMMAND variable (or the
CTEST_CVS_CHECKOUT variable) is set, its content is treated as command-line. The command is invoked with the current working directory set to the parent of the source directory, even if the source directory already exists. This can be used to create the source tree from a version control repository.
© 2000–2019 Kitware, Inc. and Contributors
Licensed under the BSD 3-clause License.