cmake: accommodate for UNIT_TEST_SOURCES
#5834
main.yml
on: push
config
7s
Matrix: win+VS build
fuzz smoke test
1m 10s
static-analysis
5m 15s
sparse
3m 26s
documentation
8m 26s
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+Meson build
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
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>0geaQaAAAAADXZOZyUN+hQpEtzxljnQ+aUEFPRURHRTA2MTcARWRnZQ==
|
win+VS build (x64)
Failed to restore: Cache service responded with 400
|
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>0g+aQaAAAAABifnvXaB72T6Vh896YvDCVRE0yRURHRTA3MTAARWRnZQ==
|
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
|
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 (9)
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.
|
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 (0)
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 (4)
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 (6)
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 (8)
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.
|
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+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 (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+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 (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+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 (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 (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 (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+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 (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 (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 (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 (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 (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 (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 (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 (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+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+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+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 (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 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 (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 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 (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 (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 (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 (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 (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 (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 (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 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
|
Artifacts
Produced during runtime
Name | Size | Digest | |
---|---|---|---|
vs-artifacts-arm64
|
27.8 MB |
sha256:c6c86e47bb2decb7be5245fc1bc49613d31300a13a63f7d111d1bbb7d8de8c8c
|
|
vs-artifacts-x64
|
28.7 MB |
sha256:42fc74b8891e54564689ab0d148047348796aa1bc48dde400fe283c000e91a33
|
|
windows-artifacts
|
98.4 MB |
sha256:d4a52c99cffd42c6d900b1a7692239b417f481eaf160f4b34de322f34625447d
|
|
windows-meson-artifacts
|
35.4 MB |
sha256:65e66f48e7541299b934054f394962b78ce1a2229dde559cfc22877876e962d9
|
|