| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Teach (create|run)_dashboard_script macros to treat the argument as the
name of a build tree. Append '.cmake' to generate the dashboard script
name. This allows future re-use of the macros for multiple test
scripts.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit "Teach CTest.Update tests to strongly check entries" (2010-02-09)
started checking Update.xml entries strongly. This revealed that some
cvs clients report "U CTestConfig.cmake" during update even though the
file did not change and it selects the same revision. As a result the
test fails with
Update.xml has extra unexpected entries:
Updated{CTestConfig.cmake}
We fix the test to tolerate this particular extra entry without failing.
|
|
|
|
|
|
|
| |
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 needs to create a cvs repository with 'cvs init', but the CVSNT
client on Windows needs 'cvs init -n' to avoid administrator access.
Previously we required users to explicitly enable CTEST_TEST_UPDATE_CVS
to activate the test on Windows.
This teaches the test to use the '-n' option when necessary. Now we can
enable the test in all cases except when trying to use a cygwin cvs.exe
without cygwin paths.
|
|
|
|
|
| |
The CTest.UpdateCVS/SVN tests report every step with a message. This
adds a message for the local modification step.
|
|
|
|
|
|
|
| |
CVS clients recognize file modifications only if a file's timestamp is
newer than its CVS/Entries line. This fixes intermittent failure of the
test on filesystems with low timestamp resolution by delaying before
creating a local modification.
|
|
|
|
|
| |
This teaches the test to create local modifications in the work tree
before updating.
|
|
|
|
|
| |
This adds a source tree subdirectory to the content of the test
projects. It also smoke tests more than one revision worth of changes.
|
|
This creates new tests "CTest.UpdateSVN" and "CTest.UpdateCVS". They
test that the Update.xml produced by CTest for a version-controlled
project contains entries for files added, changed, and removed.
|