summaryrefslogtreecommitdiffstats
path: root/Source/CTest
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'ctest-dashboard-with-modified-files'Brad King2021-02-101-1/+1
|\ | | | | | | | | | | | | 33fa015b4a CTest: Restore running dashboard client Test step with modified files Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5791
| * CTest: Restore running dashboard client Test step with modified filesBrad King2021-02-091-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit 6a6f1d1edd (CTest: exit nonzero after message(SEND_ERROR|FATAL_ERROR), 2020-04-03, v3.19.0-rc1~260^2), `ctest` no longer runs tests if there are errors before the full set of tests is defined. Such errors were previously treated more like warnings. The change exposed some cases where we were issuing an error message but proceeding to run tests anyway. The above commit downgraded one such case (missing `DartConfiguration.tcl`) to a warning explicitly in order to restore its former warning-like semantics. Downgrade the Update step's diagnostic about modified or conflicting files to a warning for the same reason. Fixes: #21783
* | clang-tidy: fix `readability-qualified-auto` warningsBen Boeckel2021-01-273-12/+12
| |
* | clang-tidy: fix `readability-make-member-function-const` warningsBen Boeckel2021-01-279-11/+11
| |
* | clang-tidy: fix `performance-no-automatic-move` warningsBen Boeckel2021-01-271-1/+1
| |
* | CTest: Save sanitizer output files after test executionPawel Dac2021-01-131-3/+9
| | | | | | | | | | | | | | Prior to this change after tests were executed output files produced by sanitizers were removed. User couldn't check in detail why test case didn't pass. Output files are kept without pid in the end.
* | Merge topic 'ctest-progress-output-fixes'Brad King2021-01-071-3/+4
|\ \ | | | | | | | | | | | | | | | | | | | | | 39cdc8afb9 ctest: Make verbose mode override progress behavior 1bcd9b06b9 ctest: Don't treat skipped test as failed tests in progess report Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5663
| * | ctest: Don't treat skipped test as failed tests in progess reportSylvain Joubert2021-01-051-3/+4
| | | | | | | | | | | | | | | Skipped tests should not stand out on their own lines Fixes #21143
* | | Code style: add missed explicit 'this->'Oleksandr Koval2021-01-0513-75/+75
|/ / | | | | | | | | CMake uses explicit 'this->' style. Using custom clang-tidy check we can detect and fix places where 'this->' was missed.
* | cmCTestBuildCommand: code improvementVitaly Stakhovsky2020-11-291-25/+18
| |
* | Merge topic 'rename_cuda_memcheck'Brad King2020-11-182-16/+16
|\ \ | |/ | | | | | | | | | | fea49b2df0 CTest: Rename CudaMemcheck to CudaSanitizer Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5514
| * CTest: Rename CudaMemcheck to CudaSanitizerTobias Ribizel2020-11-172-16/+16
| |
* | Reduce the scope of temporary cmProp variables and other improvementsVitaly Stakhovsky2020-11-051-2/+1
| |
* | include: refactor call sites of cmMakefile::ReadDependentFileAsit Dhal2020-10-211-1/+1
|/ | | | Fixes: #16773
* cmCTestBuildHandler: Avoid uninitialized line-numbersAdriaan de Groot2020-10-051-0/+2
| | | | | | | When commands fail, there is no line number to report; still initialize it explicitly to avoid compiler warnings. Issue: #21166
* CTest: add compute-sanitizer alias for cuda-memcheckTobias Ribizel2020-10-011-1/+2
|
* ctest: improve Unicode support for launchersZack Galbreath2020-09-281-4/+2
| | | | Fix launcher behavior for international characters in the path on Windows.
* ctest: report make-level errors to CDash when using launchersZack Galbreath2020-09-283-9/+27
| | | | Fixes: #19545
* ctest: split launcher XML writer into separate classZack Galbreath2020-09-284-367/+448
| | | | | This refactor will allow us to more easily add additional warnings and errors to builds that use launchers.
* Refactor: Use JSON helpers in CTest resource specKyle Edwards2020-09-092-91/+132
|
* Modernize: Use #pragma once in all header filesKitware Robot2020-09-0351-202/+51
| | | | | | | | | | | | | | | | #pragma once is a widely supported compiler pragma, even though it is not part of the C++ standard. Many of the issues keeping #pragma once from being standardized (distributed filesystems, build farms, hard links, etc.) do not apply to CMake - it is easy to build CMake on a single machine. CMake also does not install any header files which can be consumed by other projects (though cmCPluginAPI.h has been deliberately omitted from this conversion in case anyone is still using it.) Finally, #pragma once has been required to build CMake since at least August 2017 (7f29bbe6 enabled server mode unconditionally, which had been using #pragma once since September 2016 (b13d3e0d)). The fact that we now require C++11 filters out old compilers, and it is unlikely that there is a compiler which supports C++11 but does not support #pragma once.
* cmMakefile::GetDefinition: return cmPropVitaly Stakhovsky2020-09-0210-80/+90
|
* CTest: exit nonzero after message(SEND_ERROR|FATAL_ERROR)Kevin Puetz2020-08-262-10/+18
| | | | Fixes: #21004
* CTest: Add error types to cuda-memcheck parserTobias Ribizel2020-08-051-1/+2
|
* Source: use cmNonempty()Vitaly Stakhovsky2020-07-283-7/+7
|
* Merge topic 'cmctest-stdstring'Brad King2020-07-2816-80/+74
|\ | | | | | | | | | | | | 825b04c67a cmCTest: Members accept std::string parameters Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5064
| * cmCTest: Members accept std::string parametersVitaly Stakhovsky2020-07-2716-80/+74
| |
* | CTest: Prefer normative terms to express subprocess failuresRobert Maynard2020-07-271-3/+3
|/ | | | Issue: #21004
* CTest: add cuda-memcheck supportTobias Ribizel2020-07-092-0/+145
|
* Merge topic 'cmprop'Brad King2020-06-021-0/+1
|\ | | | | | | | | | | | | b36d1bdd9d Single location for cmProp typedef Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4829
| * Single location for cmProp typedefVitaly Stakhovsky2020-06-011-0/+1
| |
* | CTest: Handle non-coverage lines in gcov filesTobias Ellinghaus2020-05-291-2/+8
|/ | | | This implements a TODO in gcov file handling.
* Merge branch 'backport-ctest-repeat-notrun' into ctest-repeat-notrunBrad King2020-05-271-0/+5
|\
| * CTest: Make sure NOT_RUN tests show up in the failed test logRobert Maynard2020-05-271-0/+5
| | | | | | | | Issue: #20543
* | CTest: Log environment variables as a test measurementKyle Edwards2020-05-194-3/+40
| |
* | Refactoring: Third-parties public headers are under cm3p prefixMarc Chevrier2020-05-078-18/+16
| | | | | | | | Fixes: #20666
* | Merge topic 'stl-support'Brad King2020-05-019-12/+9
|\ \ | | | | | | | | | | | | | | | | | | 8d4a9ee398 Refactoring: rename "cm_static_string_view.hxx" as <cmext/string_view> Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4689
| * | Refactoring: rename "cm_static_string_view.hxx" as <cmext/string_view>Marc Chevrier2020-04-309-12/+9
| | |
* | | IWYU: mark <cstddef> as neededBen Boeckel2020-04-293-3/+3
|/ / | | | | | | Newer IWYU is not seeing them as needed for `size_t`.
* | Merge topic 'ctest_stop_on_failure_16628'Brad King2020-04-225-1/+21
|\ \ | | | | | | | | | | | | | | | | | | e89aeba5c4 ctest: add option --stop-on-failure Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4630
| * | ctest: add option --stop-on-failureJohnny Jazeix2020-04-205-1/+21
| | | | | | | | | | | | | | | | | | To stop the tests once one has failed Fixes: #16628
* | | Merge topic 'ctest-memcheck-sanitizers'Craig Scott2020-04-191-8/+5
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | e03d3c08f0 CTest: Fix '-T MemCheck' command-line support for sanitizers 82b6091776 Tests: Fix RunCMake.ctest_memcheck test script syntax errors Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4618
| * | CTest: Fix '-T MemCheck' command-line support for sanitizersBrad King2020-04-171-8/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In commit 49948f7221 (ctest_memcheck: Add support for ThreadSanitizer, 2014-07-07, v3.1.0-rc1~322^2~1) and commit 1e005eadbc (CTest: Fix MemoryCheckType from 'ctest -T MemCheck', 2014-07-15, v3.1.0-rc1~298^2), the `CMakeCommand` internal setting was left set only when using `ctest -S` scripts. Instead simply use CTest's corresponding CMake directly without passing it through an internal setting. Fixes: #20584
* | | Refactoring: add cm::contains to <cmext/algorithm>Marc Chevrier2020-04-175-23/+27
|/ /
* | cmParseCacheCoverage: use cmSystemTools::SplitStringBen Boeckel2020-04-132-29/+4
| |
* | nits: replace some "c" instances with 'c'Ben Boeckel2020-04-132-4/+4
| |
* | clang-tidy: address bugprone-branch-clone lintsBen Boeckel2020-04-133-31/+18
| | | | | | | | | | | | | | | | | | Arguably, many of these are bugs in `clang-tidy`. An if/else tree with other conditionals between cloned blocks may be relying on the intermediate logic to fall out of the case and inverting this logic may be non-trivial. See: https://bugs.llvm.org/show_bug.cgi?id=44165
* | CTest: Add CTEST_RESOURCE_SPEC_FILE variableKyle Edwards2020-04-023-16/+30
| |
* | Merge topic 'cmprop-getglobalprop'Brad King2020-03-271-5/+4
|\ \ | | | | | | | | | | | | | | | | | | c84cf42897 cmState::GetGlobalProperty: return cmProp Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4521
| * | cmState::GetGlobalProperty: return cmPropVitaly Stakhovsky2020-03-251-5/+4
| | |
generated by cgit v0.12 at 2025-02-11 18:41:53 (GMT)