Bill Hoffman authored Jul 27, 2017 and Brad King committed Aug 07, 2017

Since launchers show the entire stderr/stdout for a command and only
skip it if all of the lines are suppressed, it can be hard to tell if
individual suppressions are working.  Mark up the output reported to
CDash with a prefix for each line indicating whether it was a matched or
suppressed warning.  Lines that are suppressed are prefixed with
`[CTest: warning suppressed]` and lines that match the warning
expression are prefixed with `[CTest: warning matched]`. This should
make it easier for people to add suppressions as they will know what
they need to match and what they have already suppressed. This is an
issue because if there is more than one warning in a single compiler
output you have to suppress all of them before it will go away.

This commit forwards the test property PROCESSORS to CDash in the xml
produced by ctest. This is to allow CDash to know how much processor
time was allocated to a test.

* Use a parameter to select hash algorithm
* Return a std::string as result or an empty
  string if it fails
* Avoids unnecessary copy of hash value

Bill Hoffman authored Jul 11, 2017 and Brad King committed Jul 12, 2017

This passes the system exception string up to CDash and to the command line
instead of just printing "other".

Betsy McPhail authored Jun 23, 2017 and Brad King committed Jul 10, 2017

Use the '--no-subproject-summary' option to disable timing summary.

Betsy McPhail authored Jun 23, 2017 and Brad King committed Jul 10, 2017

The specified LABELS will be passed down to subdirectories as well as
any targets or tests in the directory.

Betsy McPhail authored Jun 27, 2017 and Brad King committed Jul 10, 2017

Use this variable to specify a list of labels that will be reported to
CDash as subprojects.

Allow CTest script writers to specify additional HTTP headers to be sent
to CDash during submission.

The motivating case for this feature is a corresponding change in CDash.
This will allow projects to refuse submissions from any site not bearing
a valid authentication token.

Ben Boeckel authored May 04, 2017 and Brad King committed May 04, 2017

None of these usages of `std::list` were inserting or removing elements
in the middle of the structure, so there were no benefits to using it.

Other uses were related to C pointers being stable in a list of strings
whereas in a vector of strings, small pointer optimizations could be
moved and become invalid after a modification to the hosting vector.
None of these uses modified the vector after handing out a C string to
an external store.

The new options allow the user to restrict the setup and cleanup tests
automatically added for fixtures.

The `Skipped` status is basically a runtime version of the `Disabled`
status (set as a property on the test by the configure step), so treat
them the same.

Skipped tests are neither passed nor failed tests, but return codes are
based only upon failed tests, so do not count them as such.

Fixes #16822.

There's no need to reserve 100 bytes for each of these strings.

Automate with:

git grep -l '#include <cm_' -- Source \
  | xargs sed -i 's/#include <\(cm_.*\)>/#include "\1"/g'

git grep -l '#include <cmsys/' -- Source \
  | xargs sed -i 's/#include <\(cmsys\/.*\)>/#include "\1"/g'

git grep -l '#include <cm[A-Z]' -- Source \
  | xargs sed -i 's/#include <\(cm[A-Z].*\)>/#include "\1"/g'

Betsy McPhail authored Mar 27, 2017 and Brad King committed Mar 29, 2017

When this property is set, the test is skipped and its status is
automatically set to 'Not Run'.  A disabled test will not be counted in
the total number of tests and its completion status will be 'Disabled'.

Previously, the completion status of not run tests was always set to
"Not Run".  Make it more descriptive.  This value is written to
`Test.xml` and then displayed as 'Test Details' in CDash.

Ben Boeckel authored Mar 01, 2017 and Brad King committed Mar 06, 2017

These functions just need to change the directory for a block of code
and then go back to the caller's expected location. Use
cmWorkingDirectory to ensure that all return paths are handled.

Ben Boeckel authored Mar 01, 2017 and Brad King committed Mar 06, 2017

The working directory changes here didn't really accomplish anything.

Issue: #16646

Thread failure of VC tool commands through more APIs so that we can
detect when they fail.  Defer updating of the individual VC tool usage
the future and just return true from them for now.

Since commit v3.7.0-rc1~132^2 (CTestSVN: Fix segfault when
CTEST_UPDATE_VERSION_ONLY is enabled, 2016-09-12) we do not properly
extract svn log or externals.  After updating we erase the information
that was loaded before updating and can no longer log the changes
between revisions to extract authors.

Fix this by only loading the repository information once, whether needed
by `NoteOldRevision`, `NoteNewRevision`, or both.

Fixes: #12630, #16646

Instead, prefix the error message at the two places where the errors are
handled: cmMakefile and cmCTestHandlerCommand.

Zack Galbreath authored Jan 04, 2017 and Brad King committed Jan 20, 2017

Teach the CDASH_UPLOAD signature of ctest_submit() to more thoroughly
respect the QUIET option.