0a74d7c2b8 Merge branch 'backport-ctest-repeat-notrun' into ctest-repeat-notrun
bbb62dcc72 CTest: Make sure NOT_RUN tests show up in the failed test log
c503251997 Tests: Add coverage of ctest_test RETURN_VALUE and REPEAT
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4801
bbb62dcc72 CTest: Make sure NOT_RUN tests show up in the failed test log
c503251997 Tests: Add coverage of ctest_test RETURN_VALUE and REPEAT
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4801
9812e87ee4 gitlab-ci: add a test of the VS generator based off of the ninja build
e63fe4a588 ci: add a script to run the tests with an external CMake
9893e159cc ci: support setting the generator platform and toolset
e0b9e8fba8 ci: test the configuration that was built
f00ab86f1f ci: use BOOL for boolean settings
deb5194a32 tests: avoid a warning for ctresalloc
f5e6738051 gitlab-ci: get the VS2019 location from the runner
79f3790c1a gitlab-ci: get sccache location from the runner on Windows
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4794
When testing an installed CMake, this executable does not exist.
Also remove the "or build" because we are expecting it to be built if
the target exists (and is a build failure if it fails there).
When the sccache executable is in the build directory, it can fail to be
removed if the daemon is still running when another job starts. It
continues to run when a job is canceled or fails and then is "in use"
and cannot be deleted.
GitLab now uses a `/-/` component between the `group/project` part of
the URL and the `{issues,merge_requests,tree}` part so that it can
support `group/subgroup/project` with arbitrary depth.
In commit d806bd2e8c (Tests: Update test suite to run in an Anaconda
environment, 2020-03-30) an extra `}` was left in the value of the
modified `LDFLAGS`. Remove it. While at it, simplify the code.
We run a `try_compile` with a tiny test source to check if the compiler
works so that we can fail early if it does not. When the compiler does
work, we immediately `try_compile` the ABI detection source. In the
common case that both steps work, we gain no useful information from the
first one and the work was wasted.
Re-order the checks to try the ABI detection first. If it works then
assume the compiler works and skip the dedicated check. If the ABI
check fails then proceed with the normal test for a working compiler so
the diagnostic can be shown as before.
Fixes: #18703
Brad King