| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
In commit ab9ad2a6a0 (ctest: report make-level errors to CDash when
using launchers, 2020-09-24, v3.19.0-rc1~84^2~1) we taught CTest to
capture and report errors from the build command when using launchers.
This had the unintended side effect of reporting a separate build error containing
the full build output when the build command returns non-zero. To fix this problem,
we now only report build command errors from CTest launchers when no other
more specific build errors are found.
Fixes: #23991
|
|
|
|
|
| |
The former duplicates code that is now part of the infrastructure in the
latter. The latter can also explicitly verify the results.
|
|
|
|
| |
Fixes: #19712
|
|
|
|
| |
Fixes: #19545
|
|
|
|
| |
Ignore ANSI color when scraping logs for errors and warnings
|
| |
|
|
|
|
|
|
|
|
| |
If `CTEST_USE_LAUNCHERS` is `TRUE` in a CTest script then the
`ctest_configure` command will add `-DCTEST_USE_LAUNCHERS:BOOL=TRUE` to
the cmake command used to configure the project. This allows a project
to only set `CTEST_USE_LAUNCHERS` in a ctest script and have launchers
work.
|
|
|
|
|
|
|
| |
Add variable CTEST_CHANGE_ID to configure the setting. This allows
CTest clients to give CDash information about what change is being
tested so that CDash can take actions to report the results (e.g. to a
pull request page).
|
|
|
|
| |
Add policy CMP0061 to maintain compatibility for existing projects.
|
|
|