| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
P1689 support has been merged in Clang trunk and Clang 16 branch, so we
are now able to use the finalized clang-scan-deps command line options.
See also llvm-project's clang/test/ClangScanDeps/P1689.cppm [1] for the
samples of clang-scan-deps usages.
[1] https://github.com/llvm/llvm-project/blob/6d859df46e/clang/test/ClangScanDeps/P1689.cppm
Signed-off-by: Kefu Chai <kefu.chai@scylladb.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Apply the approach from commit 354fdf2116 (ci: Reduce intermediate
docker layers and final image size, 2023-02-01) to more stages.
Also:
* Use cache (prefetch metadata and packages) to reduce network I/O
and speedup image build.
* Use `tmpfs` to drop logs produced by the package manager.
|
|
|
|
|
| |
Instead of `COPY` to get tar files, execute `RUN` w/ `--mount`.
Note that this requires the docker "buildkit" feature to be enabled.
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
12d032b265 gitlab-ci: Update NVHPC to version 22.11
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7994
|
| |
| |
| |
| | |
Fixes: #24225
|
|\ \
| |/
|/|
| |
| |
| |
| | |
004f954401 ci: Add job to test minimal CUDA install (no static libs)
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7996
|
| |
| |
| |
| |
| |
| |
| | |
Some package managers provide a minimal set of static libraries,
which historically has caused problems for FindCUDAToolkit.
Resolve this issue by creating a CUDA image with only the minimal
set of static libraries.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
a7be3c961f ci: build clang-tidy plugin in pre-build step
372ce5bffe ci: add pre-build and post-build steps to Linux
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7989
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The pre-build step will allow actions to be executed before the
CMake build but after Ninja and sccache have been downloaded, so
they can be used in the pre-build step. The env step is meant for
setting up environment variables anyway, rather than performing
actions.
The post-build step will allow extra artifacts to be computed after
the build is complete.
|
|/ |
|
|
|
|
|
| |
All our CI hosts now have Linux kernel version 3.17 or higher,
so we no longer need a dedicated tag.
|
|
|
|
|
| |
The latter tag is now available on our CI runners to more explicitly
distinguish `linux-x86_64` from `linux-aarch64`.
|
|
|
|
|
| |
This groups their definitions nicely, and makes their purpose more
clear from reference sites.
|
|
|
|
|
| |
The '_builder' part of tag entry names is not useful with our current
naming conventions.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
We already have `t:debian10-{makefiles,ninja}-clang` jobs covering old
versions of Clang with Makefile and Ninja generators. Complement them
with new `t:fedora37-{makefiles,ninja}-clang` jobs covering recent
versions of Clang.
Fedora 37 now packages LLVMFlang, so enable Fortran tests with that
compiler too.
Issue: #22387
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Revert commit 0ac9ec47f6 (ci: add clang-tidy to Debian x86_64 base
image, 2022-09-20). Our clang-tidy job runs under Fedora, and we need
the plugin to compile there anyway, so lints like IWYU will best be done
in the Fedora image.
Issue: #23912
|
|
|
|
| |
Issue: #23912
|
|
|
|
| |
Prepare to build our own clang-tidy plugin in CI.
|
| |
|
|
|
|
|
| |
Test that CMake works without its bundled dependencies.
For some dependencies, test using the minimum supported version.
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
5db79b5cd3 gitlab-ci: update to an image with git installed
3e1ace7f46 ci: add git to the CI image
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7398
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| | |
b97d371007 ci: Add OpenAL to Debian and Fedora base images
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7394
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
| |
Revert commit 5ece12b7e4 (gitlab-ci: add ISPC to the Fedora CI image,
2020-08-18, v3.19.0-rc1~244^2). Later we will download ISPC in specific
jobs.
Update a `RunCMake.NinjaMultiConfig` test expectation to account for
a change to the Qt deployed on Fedora 36.
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
b691906d27 gitlab-ci: Build qthelp-format release documentation for cmake.org
1ceec19c20 gitlab-ci: Add objects.inv to cmake.org html documentation
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7146
|
| |
| |
| |
| |
| | |
Previously the qthelp-format release documentation on `cmake.org` was
built manually.
|
|\ \
| |/ |
|
| | |
|
| |
| |
| |
| |
| | |
This was previously added in a custom branch for building the
cmake.org reference documentation.
|
| | |
|
| |
| |
| |
| | |
This enables the `JavaExportImport` test in CI.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The `native` architecture compiles for the host's GPUs, but our CI jobs
may may run on hosts with GPUs newer than supported by their version of
the CUDA toolkit. Add an undocumented environment variable to tell
CMake to clamp the native architecture to that supported by the toolkit.
Without this, we may try to compile for architectures not supported by
the CUDA Toolkit, which fails. Since commit d1b48bfabd (CUDA: Add
support for CUDA_ARCHITECTURES=native, 2022-03-04), our CUDA 9.2 CI job
fails when it runs on a CI host with a GPU architecture newer than that
CUDA 9.2 supports. Clamping the architecture level fixes that.
Do not document this clamp behavior publicly, at least for now.
Users can be responsible for building with a CUDA toolkit recent
enough to support their host's GPUs.
Issue: #22375
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
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.
|