| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| |
| |
| | |
2c140ac7b1 ci: Avoid finding Python via Windows Registry
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7203
|
| |
| |
| |
| |
| |
| |
| |
| | |
Since commit 313ea361b0 (CMake: Use FindPython instead of
FindPythonInterp to build CMake itself, 2022-04-21), CI jobs on some
Windows hosts have been finding Python via the Windows Registry.
Explicitly disable the registry search so that the CI jobs find the
Python that we download and put in the PATH inside the job.
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| | |
ca4d5d366d ci: use CMake 3.23.1
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !7172
|
| | |
|
| | |
|
| |
| |
| |
| | |
This enables the `JavaExportImport` test in CI.
|
| |
| |
| |
| |
| |
| |
| | |
In commit f9526f39a1 (ci: Add bzr and p4 to Debian and Fedora base
images, 2022-02-21) we checked the SHA-256 hash of the Perforce binary.
However, content at the download URL has changed in just the last few
weeks, so we cannot consider it stable.
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| | |
1f601753d7 gitlab-ci: add jobs testing cuda11.6 with nvcc and clang 13
7716750062 ci: add cuda11.6 base image
77bdcc949d gitlab-ci: run CUDA and HIP test jobs in any non-MR pipeline
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7038
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Compute it early enough to use in the configure step.
|
| |
| |
| |
| |
| | |
The script is a standalone ctest script that runs all steps.
It can be used for more than just external tests.
|
| |
| |
| |
| | |
The latter follows our convention for other variable names.
|
| |
| |
| |
| |
| | |
The Swift compiler is too big to put in the Debian base image,
so download it in this specific job instead.
|
| | |
|
| |
| |
| |
| |
| |
| | |
The actual compiler is too large to put in the base image.
Install its dependencies so we can download and run it in a job.
Note that Swift binaries are only available for `x86_64`.
|
| |
| |
| |
| | |
Also clean up more temporary files.
|
| |
| |
| |
| |
| | |
Avoid relying on heuristics to enable these tests.
Be sure they run in CI where expected.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Perforce does not provide binaries for `aarch64`, so leave it out for
that architecture.
Fedora now packages `breezy` instead of the original `bzr`. Note that
breezy does not have the xmloutput plugin needed for `bzr log --xml`.
This is also why commit 1972a75536 (Tests: Drop CTestUpdate.BZR test
check for xmloutput plugin, 2022-02-04) observed that there is no
`bzr xmlplugins` command.
|
| |
| |
| |
| |
| | |
Extend the change from commit 840fa28d3d (ci: Explicitly disable Java
tests on Windows, 2021-12-16) to cover Borland and Open Watcom builds.
|
| |
| |
| |
| |
| | |
Extend the change from commit 840fa28d3d (ci: Explicitly disable Java
tests on Windows, 2021-12-16) to cover LLVM/Clang builds on Windows too.
|
|/
|
|
|
| |
Add jobs covering the `clang-cl` front-end with Ninja and NMake.
Add a job covering the `clang++` front-end with Ninja.
|
|
|
|
|
|
|
|
| |
Previously we used a complicated heuristic to decide whether or not to
run the MFC test, but it sometimes decided incorrectly to run the test.
Since that was first written, we have developed a convention for other
tests to enable them via undocumented cache entries that are added only
on machines known to meet the tests' requirements. Do that for MFC.
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
45feab3c00 gitlab-ci: enable assertions on fedora34-ninja jobs
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6927
|
| |
| |
| |
| |
| |
| |
| | |
We should have at least one CI job in merge request pipelines that
builds CMake with assertions enabled. We avoid using the `Debug`
configuration in order to keep CI artifacts small, so instead use
the `Release` configuration without `-DNDEBUG`.
|
| |
| |
| |
| |
| | |
Extend the change from commit 840fa28d3d (ci: Explicitly disable Java
tests on Windows, 2021-12-16) to cover VS builds too.
|
| | |
|
| |
| |
| |
| |
| | |
Extend the change from commit 840fa28d3d (ci: Explicitly disable Java
tests on Windows, 2021-12-16) to cover VS builds too.
|
|\ \
| |/
| |
| |
| |
| |
| | |
840fa28d3d ci: Explicitly disable Java tests on Windows
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6807
|
| |
| |
| |
| |
| |
| |
| | |
Avoid searching for a Java installation on Windows hosts.
This will allow some CI hosts to have Java for other projects.
We already do this on macOS. While at it, clarify the macOS setting.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since commit 3b9975d9b5 (ci: Add JOM nightly CI job, 2021-11-17) the
`ExternalProject` test often fails spuriously with an internal error
message from JOM. Exclude it for now pending further investigation.
Prior to covering JOM in CI, it was covered by a standalone nightly
build that excluded the `ExternalProject` test for the same reason.
|
|\ \
| |/
| |
| |
| |
| |
| | |
fae34ea007 ci: add gmock to Debian base images
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6746
|
| |
| |
| |
| | |
It is already in the Fedora base images.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Previously we were relying on `VCVARSPLATFORM` and `VCVARSVERSION`
powershell script variables. Read them from the environment directly.
|
| |
| |
| |
| | |
The packages comes with the Windows SDK and/or the compiler.
|
| |
| |
| |
| |
| | |
Now that the primary VS jobs have been converted to VS 2022,
add nightly CI jobs to cover VS 2019.
|
| | |
|
| | |
|
| | |
|
|/ |
|