Merge 'readme' into HEAD #5844
main.yml
on: push
config
8s
Matrix: win+VS build
fuzz smoke test
2m 58s
static-analysis
5m 7s
sparse
3m 51s
documentation
4m 24s
Matrix: dockerized
Matrix: regular
Matrix: win+VS test
Matrix: win+Meson test
Matrix: win test
Annotations
46 errors, 40 warnings, and 34 notices
documentation
Process completed with exit code 2.
|
debian-11 (debian:11)
Process completed with exit code 2.
|
linux32 (i386/ubuntu:focal)
Process completed with exit code 2.
|
linux-breaking-changes (ubuntu:rolling)
Process completed with exit code 1.
|
linux-breaking-changes (ubuntu:rolling)
failed: t1517.350 'git survey --help-all' outside a repository
|
linux-breaking-changes (ubuntu:rolling)
failed: t1517.349 'git survey -h' outside a repository
|
linux-musl-meson (alpine:latest)
Process completed with exit code 1.
|
linux-reftable (ubuntu:rolling)
Process completed with exit code 1.
|
linux-reftable (ubuntu:rolling)
failed: t1517.352 'git survey --help-all' outside a repository
|
linux-reftable (ubuntu:rolling)
failed: t1517.351 'git survey -h' outside a repository
|
linux-meson (ubuntu:rolling)
Process completed with exit code 1.
|
linux-meson (ubuntu:rolling)
failed: t1517.320 'git survey --help-all' outside a repository
|
linux-meson (ubuntu:rolling)
failed: t1517.319 'git survey -h' outside a repository
|
almalinux-8 (almalinux:8)
Process completed with exit code 1.
|
linux-sha256 (ubuntu:rolling)
Process completed with exit code 1.
|
linux-sha256 (ubuntu:rolling)
failed: t1517.352 'git survey --help-all' outside a repository
|
linux-sha256 (ubuntu:rolling)
failed: t1517.351 'git survey -h' outside a repository
|
linux-TEST-vars (ubuntu:20.04)
Process completed with exit code 2.
|
win+Meson test (8)
Process completed with exit code 1.
|
win+VS test (5)
Process completed with exit code 1.
|
win+VS test (5)
failed: t1517.352 'git survey --help-all' outside a repository
|
win+VS test (5)
failed: t1517.351 'git survey -h' outside a repository
|
win test (5)
Process completed with exit code 1.
|
win test (5)
failed: t1517.352 'git survey --help-all' outside a repository
|
win test (5)
failed: t1517.351 'git survey -h' outside a repository
|
osx-gcc (macos-13)
Process completed with exit code 1.
|
osx-gcc (macos-13)
failed: t1517.352 'git survey --help-all' outside a repository
|
osx-gcc (macos-13)
failed: t1517.351 'git survey -h' outside a repository
|
osx-meson (macos-13)
Process completed with exit code 1.
|
osx-meson (macos-13)
failed: t1517.320 'git survey --help-all' outside a repository
|
osx-meson (macos-13)
failed: t1517.319 'git survey -h' outside a repository
|
linux-leaks (ubuntu:rolling)
Process completed with exit code 1.
|
linux-leaks (ubuntu:rolling)
failed: t1517.352 'git survey --help-all' outside a repository
|
linux-leaks (ubuntu:rolling)
failed: t1517.351 'git survey -h' outside a repository
|
osx-clang (macos-13)
Process completed with exit code 1.
|
osx-clang (macos-13)
failed: t1517.352 'git survey --help-all' outside a repository
|
osx-clang (macos-13)
failed: t1517.351 'git survey -h' outside a repository
|
linux-reftable-leaks (ubuntu:rolling)
Process completed with exit code 1.
|
linux-reftable-leaks (ubuntu:rolling)
failed: t1517.352 'git survey --help-all' outside a repository
|
linux-reftable-leaks (ubuntu:rolling)
failed: t1517.351 'git survey -h' outside a repository
|
linux-asan-ubsan (ubuntu:rolling)
Process completed with exit code 1.
|
linux-asan-ubsan (ubuntu:rolling)
failed: t1517.352 'git survey --help-all' outside a repository
|
linux-asan-ubsan (ubuntu:rolling)
failed: t1517.351 'git survey -h' outside a repository
|
osx-reftable (macos-13)
Process completed with exit code 1.
|
osx-reftable (macos-13)
failed: t1517.352 'git survey --help-all' outside a repository
|
osx-reftable (macos-13)
failed: t1517.351 'git survey -h' outside a repository
|
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>0RYaUaAAAAADKw4oEY+KiToefPmiAJ8HwQlkzRURHRTAyMTAARWRnZQ==
|
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>0RoaUaAAAAAAApg8MWEqITpUWYMK0RFWHQkwyQUEyMDMwMTA1MDUzAEVkZ2U=
|
win+VS build (arm64)
Failed to restore: Cache service responded with 400
|
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
|
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 (5)
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.
|
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
|
win+Meson test (1)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
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
|
win+Meson test (0)
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 (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.
|
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 (3)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
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-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-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 (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 (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+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 (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 (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 (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+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 (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 (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+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+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+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+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 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 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 (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 (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 (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 (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 (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 (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 (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 (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 (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
|
Artifacts
Produced during runtime
Name | Size | Digest | |
---|---|---|---|
failed-tests-linux-asan-ubsan
|
33.6 KB |
sha256:1b507f2246fbf7c54a6e85038fcfe018799b85a61e831a250705f89acad3fce5
|
|
failed-tests-linux-breaking-changes
|
33.3 KB |
sha256:ac0a240165897b47397ae20a7af8a606d6cb217aa999aca196f823d6fee1c25b
|
|
failed-tests-linux-leaks
|
33.5 KB |
sha256:c0f42f95351abc6ef927875ec57202d910b823614ffbaabd847fa00d343f54ee
|
|
failed-tests-linux-meson
|
32.7 KB |
sha256:fe107abaeb90a4e42f2295fbf68c9e11a702719dab0833fd26fa810411c74359
|
|
failed-tests-linux-reftable
|
33.7 KB |
sha256:9f420fa7cfb6a47943a8f1de6173209e7cf96d186e66de0fdcf3dcf21eb71bce
|
|
failed-tests-linux-reftable-leaks
|
33.7 KB |
sha256:99695d86ea60d76f330b46d3bbb71f36f0c8709bfbd4b601b878c2fe0f0f4a8b
|
|
failed-tests-linux-sha256
|
33.7 KB |
sha256:e2765605e50faf5ba212e6cace7f3eead60eb24502eb5ec5cd827b3345f5ee49
|
|
failed-tests-osx-clang
|
32.4 KB |
sha256:9183e0e22e0a166e00148bf6734f2f094642e78f13e17b01b82056dd0167d254
|
|
failed-tests-osx-gcc
|
32.3 KB |
sha256:130945a992d84ef8bd1fc5e97b6d691d41e739d3ef8be78041b919ab2c18f138
|
|
failed-tests-osx-meson
|
31.7 KB |
sha256:14d2aa2c8d97f2b4dd6939244cc5e8f13335ec4d60defa3886c5ae00db321738
|
|
failed-tests-osx-reftable
|
32.5 KB |
sha256:d3dd571cbbd3d342d6fe168b5bac78c48179cbe01eafd49a42d736763a8444a3
|
|
failed-tests-windows-5
|
31.4 KB |
sha256:1aaebe479a5921eb9d1e9a5445c7c15a98de50e0d73d50429d62c02a2054c96f
|
|
failed-tests-windows-vs-5
|
31.9 KB |
sha256:ae30288a039d33e957145ad948fa7008e58ffdc81eb610ddd12f2c1b82dfb7f8
|
|
vs-artifacts-arm64
|
27.8 MB |
sha256:6972fd04523523ea14abd0f8bca4dc1c89842033bafc3cd40cb72a63a2f31f3d
|
|
vs-artifacts-x64
|
28.8 MB |
sha256:333edc35ba9180da1725cb413539ebaed1d796f254a016e7d492e309e8d7e80f
|
|
windows-artifacts
|
98.9 MB |
sha256:8c26077f5a7abcded2c692229798c0ca0a3c0f548f508abb330e35247b9583d4
|
|
windows-meson-artifacts
|
35.5 MB |
sha256:17f8270352f6c838692243332c08f763f4fe57d0b844a107834f4fb078048b84
|
|