* ci-fedora33-release:
gitlab-ci: use Fedora 33 to build sources
gitlab-ci: update Linux CI to use Fedora 33
ci: update to Fedora 33 for Linux builds
ci: install gmock in the Fedora 31 image
Tests/FindBoost/TestPython: support finding 3.8 and 3.9
clang-tidy: ignore new warnings from newer versions
clang-tidy: ignore `misc-no-recursion`
The gmock libraries are referenced by GTest's CMake package files.
While at it, also explicitly install gettext. It is installed already,
but make it explicit for future testing of the FindGettext module.
(cherry picked from commit 585cc7c930)
The gmock libraries are referenced by GTest's CMake package files.
While at it, also explicitly install gettext. It is installed already,
but make it explicit for future testing of the FindGettext module.
Our test suite searches for a Python interpreter to perform some extra
checks. Our CI base images for Linux have Python available. Update our
Windows jobs to provide a Python interpreter for our test suite to find
consistently between the build and test steps.
This version is much less likely to timeout on server startup since it
runs the expensive computation in a background thread.
See https://github.com/mozilla/sccache/pull/868 for the status.
Nightly testing occasionally uncovers problems around long filenames
that were not found during gitlab-ci testing. Give a GitLab runner
a long filename to detect such problems.
Since commit 5537ccd814 (FindPython: Tests optimizations, 2020-10-01)
some FindPython tests fail because the Development component cannot be
found without knowing `CMAKE_LIBRARY_ARCHITECTURE`. Enable at least one
language in each of these test cases to get that value. This is
consistent with use in practice because the Development component does
not make much sense without a language to compile sources anyway.
Fixes: #21277
This test spuriously fails too frequently and breaks our pipelines.
Pending further investigation into the race causing the failure, skip
the test on Windows for now. The module is well covered by the test on
other platforms anyway.
Machines may have more cores than testing actually supports.
Apply the change from commit e80362252f (ci: support a max parallelism
for tests, 2020-09-28) to tests in the test-ext stage too.
Without this, we do not cover compilation with only C++11 until nightly
testing, at which point many builds require it, and failures block
merging anything that was staged.
Brad King