| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Unit test and script hook for STOP_TIME
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
create.
|
|
|
|
| |
-C configuration type string is empty.
|
|
|
|
|
|
|
|
| |
We use 'git diff-index' to detect local modifications after pull. On
some filesystems the work tree timestamps of a few files may be dated
after the index, making them appear as locally modified. We address the
problem by using 'git update-index --refresh' to refresh the index and
avoid false local modifications.
|
|
|
|
|
|
|
| |
Our internal path processing methods assume no trailing slashes, but bzr
adds trailing slashes to updated directories. This can lead to empty
entries in Update.xml files. We address the problem by stripping the
slashes as soon as they are parsed.
|
|
|
|
| |
bug causing memcheck args to be overwritten repetitively.
|
| |
|
|
|
|
|
|
| |
ctest_build and ctest_configure.
The improved text gives very clear information when either the CMakeLists.txt or CTestConfig.cmake file is missing. Hopefully, it makes it easier for those poor future souls who encounter these messages to solve their problems quickly.
|
|
|
|
| |
If APPEND is given to ctest_start, it will read the tag from the current existing Testing/TAG file rather than creating a new one based on the current time stamp. This allows a developer to run several dashboard scripts in a row, all of which will share the same tag/stamp/buildid when they finally get submitted to CDash. Now you can split the running of build phases and test phases for the same dashboard row into multiple scripts.
|
|
|
|
| |
cmCTestScriptHandler::RunConfigurationScript. This will help prevent problems like we are currently experiencing (regarding CMake continuous dashboards only running once each day because the HOME environment variable is modified indirectly by a command in a called script, but affects the environment in the calling script).
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously we produced commit times formatted like
1261403774 -0500
which is what the Git plumbing prints. Now we use a human-readable
format like
2009-12-21 15:28:06 -0500
which is still easy to machine-parse.
|
| |
|
| |
|
|
|
|
|
|
| |
Previously we escaped quotes in <UpdateCommand>...</UpdateCommand>
values using '"'. This is not necessary because the value is in
xml CDATA and not an xml attribute.
|
|
|
|
|
|
|
|
|
|
| |
A Subversion revision is unique across the entire repository, but work
trees typically correspond only to a subdirectory below the root path.
In order to specify the version of the source code that was tested,
CTest now submits a <SVNPath> element in Update.xml that specifies the
directory of the repository that corresponds to the work tree. In
combination with the revision number this uniquely specifies the tested
source. See issue #7541.
|
|
|
|
|
|
|
| |
We teach CTest to report in a <Revision> element the revision of the
source tree that was tested. This makes sense for all modern VCS tools
because they version the whole tree. We simply omit this element for
CVS because it only versions files. See issue #7541.
|
| |
|
| |
|
|
|
|
| |
the test does not pass. Also some preliminary changes for test output compression.
|
|
|
|
| |
archived and marked up individually, in order to make things easier on the CDash side. Also switched to using the NamedMeasurement tag instead of a new tag.
|
|
|
|
| |
that will be submitted to cdash using the ATTACHED_FILES test property.
|
|
|
|
| |
option. Also added parsing of html reponse output to determine whether errors or warnings were sent in response from the server. If errors or warnings occurred, the response is output to stdout, and the "submission successful" message has been changed to accurately reflect whether or not warnings or errors were returned with the response.
|
|
|
|
| |
which did not start due to missing/bad executables or missing required files.
|
|
|
|
| |
last implementation of the exe wrapper to something which makes much more sense: a REQUIRED_FILES property on tests.
|
|
|
|
| |
MPI.] Added a wrapping option to add_test so that exes built by the project can be safely wrapped in other exes and be listed as "not run" rather than "failed" if they are not built.
|
|
|
|
| |
(See BadExe test)
|
|
|
|
| |
--timeout option.
|
|
|
|
| |
timeouts if it is lower than the individual timeout.
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
| |
timeout on all tests if no more specific timeout is set on them.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In CTest command-driven script mode we support starting without a source
tree. Previously the ctest_start() command would do some initialization
but could not do anything that required CTestConfig.cmake from the input
source tree. Later, ctest_update() would run CTEST_CHECKOUT_COMMAND to
create the source tree, and then re-initialize everything. This
delayed-initialization approach led to many complicated cases of which
only some worked. For example, the second initialization only worked
correctly in Nightly mode and simply failed for Experimental and
Continuous builds.
A simpler solution is to run CTEST_CHECKOUT_COMMAND during ctest_start()
and then have a single initialization path. In principle this change in
behavior could break scripts that set the checkout command after
ctest_start() but before ctest_update(). However, the convention we've
always followed has been to set all variables before ctest_start().
See issue #9450.
|
|
|
|
| |
running ctest in showonly mode does not kill our cost store, since many ctest tests do this and corrupt our cost data.
|
| |
|
|
|
|
| |
added test coverage for passing absolute paths to subdirs.
|
|
|
|
| |
lower-indexed test depended on it.
|
|
|
|
|
|
| |
entries.
The ctest subdirs command now checks the relative path first, and if that does not exist, also checks if the given path was absolute. Thanks vodall for the patch.
|
| |
|
|
|
|
| |
not be found.
|
|
|
|
| |
ctest_build command
|
|
|
|
| |
tests are run. Previously a cycle resulted in a segfault from stack overflow.
|
|
|
|
|
| |
This may help statistically detect implicit dependencies among unit
tests while running in parallel.
|