kolan
/
CMake
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
CMake/Modules/DartConfiguration.tcl.in

113 lines
3.3 KiB
Tcl
Raw Normal View History

ENH: Fix some dart issues. Now it works fine without dart.
2003-05-02 21:57:25 +04:00
# This file is configured by CMake automatically as DartConfiguration.tcl
# If you choose not to use CMake, this file may be hand configured, by
# filling in the required variables.
# Configuration directories and files
SourceDirectory: @PROJECT_SOURCE_DIR@
BuildDirectory: @PROJECT_BINARY_DIR@
Configurable path to CTest cost data file Allow the user to set the CMake variable CTEST_COST_DATA_FILE, which will be used to store the cost data from test runs. If not set, defaults to the original location in the build tree Testing/Temporary dir.
2010-03-01 19:00:23 +03:00
# Where to place the cost data store
CostDataFile: @CTEST_COST_DATA_FILE@
ENH: Fix some dart issues. Now it works fine without dart.
2003-05-02 21:57:25 +04:00
# Site is something like machine.domain, i.e. pragmatic.crd
Site: @SITE@
# Build name is osname-revision-compiler, i.e. Linux-2.4.2-2smp-c++
BuildName: @BUILDNAME@
# Submission information
ENH: allow cdash not to trigger
2008-02-29 22:58:33 +03:00
IsCDash: @CTEST_DROP_SITE_CDASH@
Added support for CTest awareness of the CDash version. This will help forward compatibility for both tools. Note that this changeset effectively makes the default to disable output compression. Now, to enable output compression, the CDASH_CTEST_VERSION must be explicity set to >= 1.6. Automated detection of the CDash version is the next step.
2009-12-21 20:27:04 +03:00
CDashVersion: @CTEST_CDASH_VERSION@
Moved call to cache CDash version information to cmCTest::initialize. Also added a 3 second timeout when requesting the version from the server. Added an option to the CTestConfiguration that will be used to determine whether to query the version information at all. (Behavior for this setting is not yet defined.) Updated CMake's local CDash version setting to 1.6.
2010-02-08 17:47:39 +03:00
QueryCDashVersion: @CTEST_CDASH_QUERY_VERSION@
ENH: Fix some dart issues. Now it works fine without dart.
2003-05-02 21:57:25 +04:00
DropSite: @DROP_SITE@
DropLocation: @DROP_LOCATION@
DropSiteUser: @DROP_SITE_USER@
DropSitePassword: @DROP_SITE_PASSWORD@
DropSiteMode: @DROP_SITE_MODE@
DropMethod: @DROP_METHOD@
TriggerSite: @TRIGGER_SITE@
ENH: Reorganize and add subversion support
2005-02-16 21:30:17 +03:00
ScpCommand: @SCPCOMMAND@
ENH: Fix some dart issues. Now it works fine without dart.
2003-05-02 21:57:25 +04:00
# Dashboard start time
NightlyStartTime: @NIGHTLY_START_TIME@
# Commands for the build/test/submit cycle
ConfigureCommand: "@CMAKE_COMMAND@" "@PROJECT_SOURCE_DIR@"
MakeCommand: @MAKECOMMAND@
Fix issue #2336 - honor the -C arg to ctest. Honor it for all stages of running -D dashboards from the command line and running ctest_configure, ctest_build and ctest_test commands in -S scripts. Also, allow a script to change it by setting the CTEST_CONFIGURATION_TYPE variable: allows for multiple configuration build/test cycles within one script. Add a new signature for the cmake command build_command that accepts CONFIGURATION as one argument. The original build_command signature is still there, but now marked as deprecated in the documentation. Of course... also add CTestConfig tests to verify that -C is honored for -D dashboards and -S scripts.
2009-12-04 20:09:01 +03:00
DefaultCTestConfigurationType: @DEFAULT_CTEST_CONFIGURATION_TYPE@
ENH: Reorganize and add subversion support
2005-02-16 21:30:17 +03:00
ctest_update: Add CTEST_UPDATE_VERSION_ONLY option to only note the version This allows ctest_update to get the current version without actually changing the repository. This is useful when using Jenkins or an external project to update the source to a specific version, but you still want the current version to show up in CDash.
2014-08-13 21:45:08 +04:00
# version control
UpdateVersionOnly: @CTEST_UPDATE_VERSION_ONLY@
ENH: Reorganize and add subversion support
2005-02-16 21:30:17 +03:00
# CVS options
# Default is "-d -P -A"
ENH: Fix some dart issues. Now it works fine without dart.
2003-05-02 21:57:25 +04:00
CVSCommand: @CVSCOMMAND@
ENH: Reorganize and add subversion support
2005-02-16 21:30:17 +03:00
CVSUpdateOptions: @CVS_UPDATE_OPTIONS@
# Subversion options
SVNCommand: @SVNCOMMAND@
ctest_update: Tell svn not to prompt interactively (#13024) While at it, add SVNOptions/CTEST_SVN_OPTIONS configuration settings to add options to all svn invocations instead of just "svn update".
2012-09-23 21:55:48 +04:00
SVNOptions: @CTEST_SVN_OPTIONS@
ENH: Reorganize and add subversion support
2005-02-16 21:30:17 +03:00
SVNUpdateOptions: @SVN_UPDATE_OPTIONS@
Add GITCommand key value pair.
2010-05-11 17:29:55 +04:00
# Git options
GITCommand: @GITCOMMAND@
cmCTestGIT: add an option to initialize submodules on update Currently, CTest will not initialize any submodules within the already checked out source tree. Add an option to do so. The use case for not doing so is that some submodules may not be necessary for the current test and keeping network usage down may be important.
2016-03-31 19:28:46 +03:00
GITInitSubmodules: @CTEST_GIT_INIT_SUBMODULES@
Add GITCommand key value pair.
2010-05-11 17:29:55 +04:00
GITUpdateOptions: @GIT_UPDATE_OPTIONS@
ctest_update: Support custom Git update command Define CTest configuration variable CTEST_GIT_UPDATE_CUSTOM to set a custom command line for updating Git-managed source trees.
2010-06-09 00:12:28 +04:00
GITUpdateCustom: @CTEST_GIT_UPDATE_CUSTOM@
Add GITCommand key value pair.
2010-05-11 17:29:55 +04:00
ctest_update: Add support for Perforce p4 client Teach the ctest_update implementation to use the p4 command-line client to perform updates and extract the list of changes. Add a CTest.UpdateP4 test like those that exist already for the other version control tools. Make the test available when p4 and the p4d server are found. During the test launch p4d in the background to serve a repository from the test directory. Then direct the client toward this server for the duration of the test.
2013-10-23 02:11:22 +04:00
# Perforce options
P4Command: @P4COMMAND@
P4Client: @CTEST_P4_CLIENT@
P4Options: @CTEST_P4_OPTIONS@
P4UpdateOptions: @CTEST_P4_UPDATE_OPTIONS@
P4UpdateCustom: @CTEST_P4_UPDATE_CUSTOM@
ENH: Reorganize and add subversion support
2005-02-16 21:30:17 +03:00
# Generic update command
UpdateCommand: @UPDATE_COMMAND@
UpdateOptions: @UPDATE_OPTIONS@
UpdateType: @UPDATE_TYPE@
CTest-side support for compiler name and compiler version information. Requires CDash update to show on CDash.
2009-10-12 19:06:49 +04:00
# Compiler info
Compiler: @CMAKE_CXX_COMPILER@
CTest: Report to CDash the compiler version used to build the project The compiler version reported since commit v2.8.2~1018 (CTest-side support for compiler name and compiler version, 2009-10-12) only reported the version of the compiler used to build CMake, and only if it defined "_COMPILER_VERSION". Instead use the version of the compiler used to build the project CTest is testing.
2015-08-11 10:52:51 +03:00
CompilerVersion: @CMAKE_CXX_COMPILER_VERSION@
CTest-side support for compiler name and compiler version information. Requires CDash update to show on CDash.
2009-10-12 19:06:49 +04:00
CTest: Add COVERAGE_EXTRA_FLAGS cache variable (#12490) COVERAGE_EXTRA_FLAGS is a space separated value of extra flags that will be passed to gcov when ctest's coverage handler invokes gcov to do coverage analysis. Map to CoverageExtraFlags in the CTest ini file. Use default value of "-l" to match the coverage handler's earlier behavior from ctest 2.8.4 and earlier. The fix for related issue #11717 had added a " -p" which was the cause of both #12415 and #12490. Here, we revert that change to the default value, so -p is no longer there by default. The people that care to add -p may do so in their own build trees by appending " -p" to the new cache variable COVERAGE_EXTRA_FLAGS.
2011-10-22 18:38:16 +04:00
# Dynamic analysis (MemCheck)
ENH: Fix some dart issues. Now it works fine without dart.
2003-05-02 21:57:25 +04:00
PurifyCommand: @PURIFYCOMMAND@
ValgrindCommand: @VALGRIND_COMMAND@
ValgrindCommandOptions: @VALGRIND_COMMAND_OPTIONS@
CTest: Fix MemoryCheckType from 'ctest -T MemCheck' Before this commit, you would have to run ctest -S mode to get MemoryCheckType to work. This is because CMAKE_COMMAND was not set. The fix is to use cmSystemTools::GetCMakeCommand instead.
2014-07-15 22:19:14 +04:00
MemoryCheckType: @MEMORYCHECK_TYPE@
ctest: add support for additional sanitizer options Sanitizers receive options through their environment variable; support user-specified options here.
2014-10-03 21:45:07 +04:00
MemoryCheckSanitizerOptions: @MEMORYCHECK_SANITIZER_OPTIONS@
ENH: Add initial memory check support which works for Valgrind
2003-12-16 01:26:00 +03:00
MemoryCheckCommand: @MEMORYCHECK_COMMAND@
MemoryCheckCommandOptions: @MEMORYCHECK_COMMAND_OPTIONS@
ENH: Add suppression file
2003-12-17 00:19:32 +03:00
MemoryCheckSuppressionFile: @MEMORYCHECK_SUPPRESSIONS_FILE@
CTest: Add COVERAGE_EXTRA_FLAGS cache variable (#12490) COVERAGE_EXTRA_FLAGS is a space separated value of extra flags that will be passed to gcov when ctest's coverage handler invokes gcov to do coverage analysis. Map to CoverageExtraFlags in the CTest ini file. Use default value of "-l" to match the coverage handler's earlier behavior from ctest 2.8.4 and earlier. The fix for related issue #11717 had added a " -p" which was the cause of both #12415 and #12490. Here, we revert that change to the default value, so -p is no longer there by default. The people that care to add -p may do so in their own build trees by appending " -p" to the new cache variable COVERAGE_EXTRA_FLAGS.
2011-10-22 18:38:16 +04:00
# Coverage
ENH: Improve coverage on systems with multiple gcov commands
2003-12-08 19:23:46 +03:00
CoverageCommand: @COVERAGE_COMMAND@
CTest: Add COVERAGE_EXTRA_FLAGS cache variable (#12490) COVERAGE_EXTRA_FLAGS is a space separated value of extra flags that will be passed to gcov when ctest's coverage handler invokes gcov to do coverage analysis. Map to CoverageExtraFlags in the CTest ini file. Use default value of "-l" to match the coverage handler's earlier behavior from ctest 2.8.4 and earlier. The fix for related issue #11717 had added a " -p" which was the cause of both #12415 and #12490. Here, we revert that change to the default value, so -p is no longer there by default. The people that care to add -p may do so in their own build trees by appending " -p" to the new cache variable COVERAGE_EXTRA_FLAGS.
2011-10-22 18:38:16 +04:00
CoverageExtraFlags: @COVERAGE_EXTRA_FLAGS@
ENH: Fix some dart issues. Now it works fine without dart.
2003-05-02 21:57:25 +04:00
Fixed ctest output where max test index is not the same width as the total number of tests. Also some preliminary changes for batching ctest jobs
2009-09-02 18:08:40 +04:00
# Cluster commands
SlurmBatchCommand: @SLURM_SBATCH_COMMAND@
SlurmRunCommand: @SLURM_SRUN_COMMAND@
ENH: Fix some dart issues. Now it works fine without dart.
2003-05-02 21:57:25 +04:00
# Testing options
# TimeOut is the amount of time in seconds to wait for processes
# to complete during testing. After TimeOut seconds, the
Fixed ctest output where max test index is not the same width as the total number of tests. Also some preliminary changes for batching ctest jobs
2009-09-02 18:08:40 +04:00
# process will be summarily terminated.
ENH: Fix some dart issues. Now it works fine without dart.
2003-05-02 21:57:25 +04:00
# Currently set to 25 minutes
TimeOut: @DART_TESTING_TIMEOUT@
ENH: Create include(CTest) launcher interface This defines a new CTest configuration variable CTEST_USE_LAUNCHERS. When set to true it puts 'ctest --launch' in RULE_LAUNCH_* properties and enables the CTest configuration option 'UseLaunchers'. Currently this works only for Makefile generators.
2009-02-11 23:18:13 +03:00
ctest: Optionally avoid starting tests that may exceed a given CPU load Add a TestLoad setting to CTest that can be set via a new --test-load command-line option, CTEST_TEST_LOAD variable, or TEST_LOAD option to the ctest_test command. Teach cmCTestMultiProcessHandler to measure the CPU load and avoid starting tests that may take more than the spare load currently available. The expression <current_load> + <test_processors> <= <max-load> must be true to start a new test. Co-Author: Zack Galbreath <zack.galbreath@kitware.com>
2015-06-09 15:50:44 +03:00
# During parallel testing CTest will not start a new test if doing
# so would cause the system load to exceed this value.
TestLoad: @CTEST_TEST_LOAD@
ENH: Create include(CTest) launcher interface This defines a new CTest configuration variable CTEST_USE_LAUNCHERS. When set to true it puts 'ctest --launch' in RULE_LAUNCH_* properties and enables the CTest configuration option 'UseLaunchers'. Currently this works only for Makefile generators.
2009-02-11 23:18:13 +03:00
UseLaunchers: @CTEST_USE_LAUNCHERS@
ENH: add ability to control ssl cert checking
2009-04-10 20:15:03 +04:00
CurlOptions: @CTEST_CURL_OPTIONS@
ENH: make sure CTEST_CURL_OPTIONS work from script mode
2009-04-17 22:44:01 +04:00
# warning, if you add new options here that have to do with submit,
# you have to update cmCTestSubmitCommand.cxx
Checksums on CTest submit files, and retry timed out submissions.
2010-06-03 18:34:34 +04:00
# For CTest submissions that timeout, these options
# specify behavior for retrying the submission
Cross-platform fixes for checksum/retry code
2010-06-03 21:27:26 +04:00
CTestSubmitRetryDelay: @CTEST_SUBMIT_RETRY_DELAY@
CTestSubmitRetryCount: @CTEST_SUBMIT_RETRY_COUNT@