Skip to content

Merge 'readme' into HEAD #5839

Merge 'readme' into HEAD

Merge 'readme' into HEAD #5839

Triggered via push August 5, 2025 09:44
Status Failure
Total duration 49m 39s
Artifacts 17

main.yml

on: push
Matrix: win+VS build
win+Meson build
4m 39s
win+Meson build
Matrix: dockerized
Matrix: regular
Matrix: win+VS test
Matrix: win+Meson test
Matrix: win test
Fit to window
Zoom out
Zoom in

Annotations

45 errors, 40 warnings, and 34 notices
linux-musl-meson (alpine:latest)
Process completed with exit code 1.
almalinux-8 (almalinux:8)
Process completed with exit code 1.
debian-11 (debian:11)
Process completed with exit code 2.
linux-sha256 (ubuntu:rolling)
Process completed with exit code 1.
linux-sha256 (ubuntu:rolling)
failed: t1517.348 'git survey --help-all' outside a repository
linux-sha256 (ubuntu:rolling)
failed: t1517.347 'git survey -h' outside a repository
linux-breaking-changes (ubuntu:rolling)
Process completed with exit code 1.
linux-breaking-changes (ubuntu:rolling)
failed: t1517.346 'git survey --help-all' outside a repository
linux-breaking-changes (ubuntu:rolling)
failed: t1517.345 'git survey -h' outside a repository
linux-TEST-vars (ubuntu:20.04)
Process completed with exit code 2.
linux32 (i386/ubuntu:focal)
Process completed with exit code 2.
win+VS test (5)
Process completed with exit code 1.
win+VS test (5)
failed: t1517.348 'git survey --help-all' outside a repository
win+VS test (5)
failed: t1517.347 'git survey -h' outside a repository
linux-meson (ubuntu:rolling)
Process completed with exit code 1.
linux-meson (ubuntu:rolling)
failed: t1517.316 'git survey --help-all' outside a repository
linux-meson (ubuntu:rolling)
failed: t1517.315 'git survey -h' outside a repository
linux-reftable (ubuntu:rolling)
Process completed with exit code 1.
linux-reftable (ubuntu:rolling)
failed: t1517.348 'git survey --help-all' outside a repository
linux-reftable (ubuntu:rolling)
failed: t1517.347 'git survey -h' outside a repository
osx-clang (macos-13)
Process completed with exit code 1.
osx-clang (macos-13)
failed: t1517.348 'git survey --help-all' outside a repository
osx-clang (macos-13)
failed: t1517.347 'git survey -h' outside a repository
osx-reftable (macos-13)
Process completed with exit code 1.
osx-reftable (macos-13)
failed: t1517.348 'git survey --help-all' outside a repository
osx-reftable (macos-13)
failed: t1517.347 'git survey -h' outside a repository
win+Meson test (7)
Process completed with exit code 1.
osx-meson (macos-13)
Process completed with exit code 1.
osx-meson (macos-13)
failed: t1517.316 'git survey --help-all' outside a repository
osx-meson (macos-13)
failed: t1517.315 'git survey -h' outside a repository
linux-leaks (ubuntu:rolling)
Process completed with exit code 1.
linux-leaks (ubuntu:rolling)
failed: t1517.348 'git survey --help-all' outside a repository
linux-leaks (ubuntu:rolling)
failed: t1517.347 'git survey -h' outside a repository
linux-reftable-leaks (ubuntu:rolling)
Process completed with exit code 1.
linux-reftable-leaks (ubuntu:rolling)
failed: t1517.348 'git survey --help-all' outside a repository
linux-reftable-leaks (ubuntu:rolling)
failed: t1517.347 'git survey -h' outside a repository
linux-asan-ubsan (ubuntu:rolling)
Process completed with exit code 1.
linux-asan-ubsan (ubuntu:rolling)
failed: t1517.348 'git survey --help-all' outside a repository
linux-asan-ubsan (ubuntu:rolling)
failed: t1517.347 'git survey -h' outside a repository
win test (5)
Process completed with exit code 1.
win test (5)
failed: t1517.348 'git survey --help-all' outside a repository
win test (5)
failed: t1517.347 'git survey -h' outside a repository
osx-gcc (macos-13)
Process completed with exit code 1.
osx-gcc (macos-13)
failed: t1517.348 'git survey --help-all' outside a repository
osx-gcc (macos-13)
failed: t1517.347 '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+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>0vNKRaAAAAACMyOSDpG7wQKb2DtNkJwi+QkwyQUEyMDMwMTA4MDA1AEVkZ2U=
win+VS build (arm64)
Failed to restore: Cache service responded with 400
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>0v9KRaAAAAACJiLolMYOKQoKqlxN6xLSxQ0gxRURHRTA5MTEARWRnZQ==
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.
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
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 (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 (0)
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 (3)
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-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 test (7)
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 (1)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
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-gcc (macos-13)
JGit wasn't installed, see above for clues why
osx-gcc (macos-13)
Already linked: /usr/local/Cellar/gettext/0.26
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+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 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 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 (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+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+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 (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 (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 (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 (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 (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 (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+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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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
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

Artifacts

Produced during runtime
Name Size Digest
failed-tests-linux-asan-ubsan
33.3 KB
sha256:10b05b6f4bbcfb423e0f367b6d702ed3249c906ba9902ffaa38fee9cec04d6a7
failed-tests-linux-breaking-changes
33.1 KB
sha256:e9937908de06d1154378ec0beba8414526f153376e0e8bf49a8d6bdd74de9d64
failed-tests-linux-leaks
33.3 KB
sha256:197dc27e5588a52223e0afb701666dcdfa1292b215acd148e6e5b5eed2fbb72f
failed-tests-linux-meson
32.5 KB
sha256:f4d0baedfb8315f480eb99ba02a679f875a0b04e7284ee0662126c24c50906a9
failed-tests-linux-reftable
33.5 KB
sha256:f0773ed9e2f6eb17963025c91a640098496bfa282992fc54ee289b799a3b0db0
failed-tests-linux-reftable-leaks
33.4 KB
sha256:b042a596314487d7c153b3e6b1ce15d6e102fc0b487e9c5ed44170f9babb51b7
failed-tests-linux-sha256
33.5 KB
sha256:c62ae27f52910e01c8634c0654aa6ed261512ef8764f79637e1478dcfcfc20db
failed-tests-osx-clang
32.1 KB
sha256:efd3195d8ae5ee6264a8ecdc957b7fe14d6704bbce030785c9dfb01a5071cc54
failed-tests-osx-gcc
32.1 KB
sha256:94771af8271bf3d7c23fc0ddcf2d7db7d4b2b9f2e7cb1f914332b0a7643ddd0b
failed-tests-osx-meson
31.4 KB
sha256:71bc1353aa335d86b64643a04f71585e4561fb791e31d08a39e56250ad1207ee
failed-tests-osx-reftable
32.3 KB
sha256:ba9b56d8206b9af90eeb1c8d259c7869c4ed693ebd9422ea93c9ea8a6debec22
failed-tests-windows-5
31.2 KB
sha256:b0dd379ddb7a76615fb343b0b8276d856616e65a01fb190a0cef277577ca7578
failed-tests-windows-vs-5
31.7 KB
sha256:62b2ec1f6f80ae8fd9e9ebbefcc719713739e711df811551d58d951a49177b4b
vs-artifacts-arm64
27.8 MB
sha256:77fd2a083e5a00b5dbfa36530243341f6dca68346bd0e6e5895ac2faae028fbd
vs-artifacts-x64
28.8 MB
sha256:f786691ff8dd5eba2680661e2d457d67cf32ec6a70f0b8172ac078aa4a5a419d
windows-artifacts
98.8 MB
sha256:c08cbea8219d35c9b20a4f82cf043fb5691adf083ced0616dc8fa24a90fd3a0f
windows-meson-artifacts
35.5 MB
sha256:dd70570c16d250db704da112af9cc3895a9a199f4187952b6a1b6a186e6b857f