| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Since CTest does not currently load configuration settings computed at
CMake Configure time while running dashboard scripts, the ctest_build
command must honor the CTEST_USE_LAUNCHERS option directly.
|
|
|
|
|
| |
This teaches cmCTestLaunch to report source files that lie under the top
source directory relative to the top.
|
|
|
|
|
|
| |
When we collect Build.xml fragments generated by 'ctest --launch', this
lexicographically orders fragments with the same time stamp on disk
instead of incorrectly dropping duplicates.
|
|
|
|
|
|
|
|
|
|
|
| |
This defines a 'UseLaunchers' CTest configuration option. When enabled,
CTest skips log scraping from the Build step output. Instead it defines
the environment variable CTEST_LAUNCH_LOGS to a log directory during the
build. After the build it looks for error-*.xml and warning-*.xml files
containing fragments for inclusion in Build.xml and submission.
This is useful in conjuction with 'ctest --launch' and the RULE_LAUNCH_*
properties to get reliable, highly-granular build failure reports.
|
|
|
|
|
|
| |
cmCTestLaunch first used an empty initializer list to zero-initialize a
buffer, but this is not supported on older compilers. Instead we avoid
the need for initialization altogether.
|
|
|
|
|
|
|
| |
This creates an undocumented 'ctest --launch' mode. It launches a
specified command and optionally records a failure in an xml fragment.
We will optionally use this in CTest's Build stage to record per-rule
build failure information when using Makefile generators.
|
| |
|
| |
|
|
|
|
|
|
|
| |
This class provides easy syntax to efficiently insert blocks of data
into XML documents with proper escapes. It replaces the old
cmCTest::MakeXMLSafe and cmSystemTools::MakeXMLSafe methods which
allocated extra memory instead of directly streaming the data.
|
|
|
|
|
|
| |
This moves the error/warning count summary printed by
cmCTestBuildHandler to after Build.xml is generated. Later we will
compute the counts during generation of the xml.
|
|
|
|
|
|
|
| |
This divides cmCTestBuildHandler::GenerateDartBuildOutput into three
methods to generate the header, content, and footer components of
Build.xml files. It will allow the content generation to be replaced
later.
|
|
|
|
| |
STL. Use explicit iteration to insert individual elements one at a time. Sigh.
|
|
|
|
| |
setting properly to the ctest configuration during a submit. Also, do not propagate TriggerSite for projects submitting to CDash. No triggers are necessary with CDash.
|
|
|
|
|
|
|
| |
This refactors generation of <Test> element headers and footers in
cmCTestTestHandler and re-uses it in cmCTestMemCheckHandler. The change
removes duplicate code and enables the new <Labels> element for MemCheck
results.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
We need to initialize cmCTestSubmitHandler on construction to make sure
all parts get enabled by default. The recent fix to re-enable all parts
on initialization broke submit-only operations because the handler did
not initialize on construction. This also removes duplicate
initialization code.
|
|
|
|
| |
generated XML files are valid, parse-able XML.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The Borland 5.5 compiler's STL set does not define correct signatures
for its find() members, leading to build errors. This works around the
problem.
|
|
|
|
|
| |
This adds a PARTS option to the ctest_submit command which tells it to
submit only parts whose names are listed with the option.
|
|
|
|
|
|
| |
This splits the list of files for CTest to submit into those belonging
to each part. The set is recombined just before submission. Later this
will allow piecewise submissions.
|
|
|
|
|
| |
This adds an APPEND option to the ctest_* commands which tells them to
put the Append="true" attribute in the Site element of their XML file.
|
|
|
|
|
|
|
| |
The previous approach to handling of arguments to ctest_* commands
worked only for keyword/value arguments with a single value. This
refactors the approach to allow some commands to define alternative
argument forms.
|
| |
|
|
|
|
|
| |
This teaches CTest to send the test property "LABELS" in Test.xml
dashboard submissions as Label elements inside a Labels element.
|
|
|
|
|
|
|
| |
This moves management of the LC_MESSAGES environment variable into an
automatic variable. Previously if an error occurred the original
environment value was not restored. This makes the fix to issue #5936
more robust.
|
| |
|
|
|
|
| |
pass -D arguments to the cmake configure step from a ctest -S script. Also clarify/correct some not so helpful error messages.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
When ctest --build-and-test runs the --test-command its output did not
quote the arguments of the command being tested making it difficult to
read. This adds the quotes. This also changes the wording of the
failure case to not sound like CTest could not run the executable when
in fact it ran and returned failure.
|
|
|
|
| |
variables on a per-test basis for ctest using set_test_properties ENVIRONMENT.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
executing a ctest script so the search paths are fully set up and variables
like CMAKE_SYSTEM are available. This is useful e.g. for new-style ctest
scripting.
(these files are also loaded on startup by cpack, so now they behave
similar).
Hmmm, maybe they should be also loaded by cmake -P ?
Alex
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The output of "cvs update" contains a line such as one of
cvs update: `foo.txt' is no longer in the repository
cvs update: foo.txt is no longer in the repository
cvs update: warning: foo.txt is not (any longer) pertinent
when file "foo.txt" has been removed in the version to which the update
occurs. Previously only the first case would be recognized. This fixes
the regular expression to match all these cases.
|
| |
|
|
|
|
| |
and cvs
|
| |
|
|
|
|
| |
Alex
|
| |
|
|
|
|
| |
thing on the dashbaord
|
| |
|