| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| | |
82fbf490 cmCTestTestHandler: take reference to temporary string instead of doing a copy
|
| |
| |
| |
| | |
This will increase the lifetime of the temporary until the end of the function.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
e2a489c7 Remove some temporary vectors for ExpandListArgument.
0f99feec cmGeneratorExpression: Remove unused header.
722f1a71 CTest: Expand a string directly into a container.
|
| |/
| |
| |
| | |
Expand directly into the target when possible.
|
|/
|
|
|
| |
Print file name instead of line content for "Looks like there are more
lines in the file:" error message.
|
|\
| |
| |
| |
| | |
1c812979 ctest_memcheck: Do not open empty BC output file name
|
| |
| |
| |
| |
| |
| | |
In cmCTestMemCheckHandler::PostProcessBoundsCheckerTest return early
if the output file name is empty. We already do this in the similar
cmCTestMemCheckHandler::AppendMemTesterOutput method.
|
|/
|
|
|
|
| |
Remove code from cmParseBlanketJSCoverage.cxx and
cmParseDelphiCoverage.cxx which caused scanbuild errors
about not reading the value that was stored.
|
|
|
|
|
|
|
| |
In the unlikely event that someone has a billion+ scripts (or some
codepath returns negative numbers), we could overflow and make a pile of
errors a non-error. This change also allows us to use flags for the
error in the future rather than just "something went wrong".
|
|
|
|
|
|
| |
Because ctest reads in binary but writes in text mode, Windows' newline
transformation can be applied multiple times causing '\n' in the source
application to be written out as '\r\r\n' instead.
|
| |
|
|
|
|
|
|
|
| |
Add a coverage parser for the Blanket.js library using the JSON output of
the mocha.js test runner.
Add a test for the new parser.
|
|\
| |
| |
| |
| | |
2db55ffa Remove borland workarounds.
|
| |
| |
| |
| |
| | |
CMake 3.0 is the last release to require to be able to build with
Borland.
|
|\ \
| | |
| | |
| | |
| | | |
cc1139cc strings: Remove redundant calls to std::string::c_str()
|
| |/
| |
| |
| |
| | |
Replacements were detected and performed by the clang tool
remove-cstr-calls on a linux build.
|
|\ \
| |/
|/|
| |
| | |
5c31c3e4 CTest: Add code coverage parser for Pascal/Delphi
|
| |
| |
| |
| |
| |
| |
| |
| | |
Add a class to parse the HTML output of the Delphi-code-coverage tool
http://code.google.com/p/delphi-code-coverage/
Add a test for the new parser.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
e0e75a72 Help: Add notes for topic 'ctest-memcheck-sanitizers'
7345a1f7 tests: Add a test for ctest_memcheck MemorySanitizer
0c6330da ctest_memcheck: Add support for MemorySanitizer msan
9ba8bf12 tests: add a test for ctest_memcheck UndefinedBehaviorSanitizer
816c100a ctest_memcheck: Add support for UndefinedBehaviorSanitizer ubsan
b67ef537 ctest_memcheck: Order sanitizer type code consistently
f48a2968 Tests: Organize CTestTestMemcheck inner test code
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
UBSan instruments a build and logs messages on any undefined behavior
instances.
|
| | |
| | |
| | |
| | | |
Use alphabetic order everywhere we enumerate the sanitizer types.
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
f25e431d tests: set sanitizer options properly
f0661bf3 tests: fix copy/paste from tsan -> asan comments
ca9cc25c ctest: add support for additional sanitizer options
0b9ffffc ctest: update documentation for CTEST_MEMORYCHECK_TYPE
|
| | |
| | |
| | |
| | |
| | | |
Sanitizers receive options through their environment variable; support
user-specified options here.
|
| | |
| | |
| | |
| | |
| | |
| | | |
The AddressSanitizer value was not documented.
Also fix some typos.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
42e39bb3 Fix a few more places to use cmsys::[io]fstream instead of std::fstream.
|
| |/ / |
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
When the file is not found in $CMAKE_SOURCE_DIR/<file path>,
the CurFileName pointer remained set to the previous file. This
caused the new file's coverage data to populate the into the
wrong object giving incorrect results and occasionally resulting
in a seg fault.
|
|/
|
|
| |
This is less verbose than defining CMAKE_GENERATOR_PLATFORM.
|
|
|
|
|
|
|
|
|
|
| |
The ctest_configure command already reads the CTEST_CMAKE_GENERATOR
variable to get the value for the cmake -G option. Read new variable
CTEST_CMAKE_GENERATOR_PLATFORM to pass on as CMAKE_GENERATOR_PLATFORM.
The "ctest --build-and-test" mode already has "--build-generator" to
specify the -G option to CMake. Add a "--build-generator-platform" option
to specify a value to pass on as CMAKE_GENERATOR_PLATFORM.
|
|\
| |
| |
| |
| | |
6d66e396 CTEST: Fix MUMPS file parser and update test
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The current file parser for a MUMPS routine uses a period "." as the
one of the signals that a line of MUMPS code is executable. This is not
a correct assumption. Add the period to the list of characters that CTest
will not consider the start of a line of code.
Update the test routine to have an entry point with code to match the scenario
mentioned above.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Prior to this change / was not allowed in the build name. This was tested
with a CDash server and worked. In addition the safe build name was not
used everywhere. This caused mismatched build names to be in the xml
files going to CDash which caused different rows to be created for the
same build.
|
|/
|
|
|
|
|
| |
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.
|
|\
| |
| |
| |
| | |
b35a7730 Fix truncation of valgrind output logic.
|
| |
| |
| |
| |
| |
| | |
This showed up because scan-build noticed outputFull was basically
a constant. Logic should be output all valgrind output. Then output
regular test output until output limit is reached.
|
|/
|
|
|
| |
This avoids having to check the pointer value at each use which
was not being done.
|
|
|
|
|
|
| |
No call sites pass NULL to the output argument, so take it by
reference to avoid the if(output) conditions. Propagate the
change through the TryCompile APIs that call it.
|
|
|
|
|
|
|
|
|
|
| |
Add a new additional entry to the FilePaths array when a
"package" tag has been found. This path should consist of the package
information found appended to the projects source directory.
This change will allow code held in a /src/main/java/* directory off of the
projects source directory to be found, unlike now which assumes a subdirectory
contains the code.
|
|
|
|
|
|
| |
Since the Sanitizers write out one log file per process, a single
test might have more than one log file. This commit allows ctest
to read all of the log files found for a particual test.
|
|\
| |
| |
| |
| | |
09b2ac38 Encoding: Fix a few encoding problems with ctest.
|
| |
| |
| |
| |
| | |
This also fixes some test failures on Windows when the
name of the build directory contains non-ascii characters.
|
| |
| |
| |
| |
| |
| | |
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.
|
|/
|
|
|
|
| |
This adds support for memory and leak sanitizers. This is built into
clang and gcc 4.8 and new compilers. It is activated with a -f switch
during compile.
|
|
|
|
|
|
|
|
|
| |
This commit adds support for ThreadSanitizer to ctest. ThreadSanitizer
is part of the clang compiler and also gcc 4.8 and later. You have to
compile the code with special flags. Then your code gets the the
ThreadSanitizer ability built into it. To pass options to the
ThreadSanitizer you use an environment variable. This commit teaches
ctest to parse the output from ThreadSanitizer and send it to CDash.
|
|
|
|
|
|
| |
Send status messages to the CTest HANDLER_OUTPUT log since they are part
of the script handler output. This also ensures they appear inline with
other test command handler output.
|
|\
| |
| |
| |
| | |
f7303131 CTest: Teach the launchers to honer the max warnings and errors
|
| |
| |
| |
| |
| |
| | |
The ctest launcher code did not respect the number of errors and
warnings limits. Limit the number of launcher report fragments that we
report in the final submission.
|
|/
|
|
|
| |
This class had a method that started with lower case, and also
was called without this->.
|