cmake: accommodate for UNIT_TEST_SOURCES
#5831
main.yml
on: push
config
6s
Matrix: win+VS build
fuzz smoke test
1m 14s
static-analysis
5m 3s
sparse
3m 20s
documentation
9m 53s
Matrix: dockerized
Matrix: regular
Matrix: win+VS test
Matrix: win+Meson test
Matrix: win test
Annotations
40 warnings and 34 notices
pedantic (fedora:latest)
JGit wasn't installed, see above for clues why
|
pedantic (fedora:latest)
git-lfs wasn't installed, see above for clues why
|
pedantic (fedora:latest)
perforce wasn't installed, see above for clues why
|
win+VS build (x64)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0iUCQaAAAAAAaHf2KAj+9T479UdjCeD7GQ0hHRURHRTE3MDkARWRnZQ==
|
win+VS build (x64)
Failed to restore: Cache service responded with 400
|
win+Meson build
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
win+VS build (arm64)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0j0CQaAAAAAALkgnf3ga2QZAfHxmZxpb1QkwyQUEyMDMwMTEwMDA3AEVkZ2U=
|
win+VS build (arm64)
Failed to restore: Cache service responded with 400
|
linux-musl-meson (alpine:latest)
JGit wasn't installed, see above for clues why
|
linux-musl-meson (alpine:latest)
git-lfs wasn't installed, see above for clues why
|
linux-musl-meson (alpine:latest)
perforce wasn't installed, see above for clues why
|
almalinux-8 (almalinux:8)
JGit wasn't installed, see above for clues why
|
almalinux-8 (almalinux:8)
git-lfs wasn't installed, see above for clues why
|
almalinux-8 (almalinux:8)
perforce wasn't installed, see above for clues why
|
linux32 (i386/ubuntu:focal)
JGit wasn't installed, see above for clues why
|
linux32 (i386/ubuntu:focal)
git-lfs wasn't installed, see above for clues why
|
linux32 (i386/ubuntu:focal)
perforce wasn't installed, see above for clues why
|
win+Meson test (6)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
debian-11 (debian:11)
JGit wasn't installed, see above for clues why
|
debian-11 (debian:11)
git-lfs wasn't installed, see above for clues why
|
debian-11 (debian:11)
perforce wasn't installed, see above for clues why
|
win+Meson test (0)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
win+Meson test (7)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
win+Meson test (5)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
win+Meson test (3)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
win+Meson test (2)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
win+Meson test (9)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
win+Meson test (8)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
win+Meson test (1)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
win+Meson test (4)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
osx-clang (macos-13)
JGit wasn't installed, see above for clues why
|
osx-clang (macos-13)
Already linked: /usr/local/Cellar/gettext/0.26
|
osx-gcc (macos-13)
JGit wasn't installed, see above for clues why
|
osx-gcc (macos-13)
Already linked: /usr/local/Cellar/gettext/0.26
|
osx-meson (macos-13)
JGit wasn't installed, see above for clues why
|
osx-meson (macos-13)
pcre2 10.45 is already installed and up-to-date.
To reinstall 10.45, run:
brew reinstall pcre2
|
osx-meson (macos-13)
ninja 1.13.1 is already installed and up-to-date.
To reinstall 1.13.1, run:
brew reinstall ninja
|
osx-meson (macos-13)
Already linked: /usr/local/Cellar/gettext/0.26
|
osx-reftable (macos-13)
JGit wasn't installed, see above for clues why
|
osx-reftable (macos-13)
Already linked: /usr/local/Cellar/gettext/0.26
|
win+VS build (x64)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+Meson build
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+VS build (arm64)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win build
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+Meson test (6)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+Meson test (0)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+Meson test (7)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+Meson test (5)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+Meson test (3)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+Meson test (2)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+Meson test (9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+VS test (7)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+Meson test (8)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+VS test (8)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+Meson test (1)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+Meson test (4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+VS test (0)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+VS test (3)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+VS test (1)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+VS test (4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+VS test (6)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+VS test (5)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+VS test (2)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win test (8)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win+VS test (9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win test (1)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win test (4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win test (5)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win test (7)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win test (9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win test (6)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win test (2)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win test (3)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
win test (0)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
Artifacts
Produced during runtime
Name | Size | Digest | |
---|---|---|---|
vs-artifacts-arm64
|
27.7 MB |
sha256:13f868cb6dccc4f864f92356e999980fc2a831fcea5aac3181c5511268766d9a
|
|
vs-artifacts-x64
|
28.7 MB |
sha256:f744503f09b0f323013d68f5546c3b8ce5159b21589e4d2e172f0a6686934045
|
|
windows-artifacts
|
98.4 MB |
sha256:9ac555fd2234205b1838e51fde4916948b99a626a0b62a5400b7a95221aac6c9
|
|
windows-meson-artifacts
|
35.4 MB |
sha256:32be9ca146f2c3f32f2665f325ceb8f15af67743dac5aabe8f817ac4355fa4d3
|
|