Skip to content

Merge 'readme' into HEAD #5856

Merge 'readme' into HEAD

Merge 'readme' into HEAD #5856

Triggered via push August 10, 2025 01:44
Status Failure
Total duration 54m 56s
Artifacts 17

main.yml

on: push
Matrix: win+VS build
win+Meson build
3m 28s
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.
debian-11 (debian:11)
Process completed with exit code 2.
linux32 (i386/ubuntu:focal)
Process completed with exit code 2.
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-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-TEST-vars (ubuntu:20.04)
Process completed with exit code 2.
win+Meson test (8)
Process completed with exit code 1.
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-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-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
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
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
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
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
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
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
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>0wvmXaAAAAAAkOM8b18AmR7LMSsKDFXQUQkwyQUEyMDMwMTA5MDQ1AEVkZ2U=
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>0wvmXaAAAAABgJbaQkvXdSZvXRZ2A6tq9QlkzRURHRTA1MTkARWRnZQ==
win+VS build (arm64)
Failed to restore: Cache service responded with 400
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
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
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
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 (6)
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 (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 (4)
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 (1)
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-clang (macos-13)
JGit wasn't installed, see above for clues why
osx-clang (macos-13)
Already linked: /usr/local/Cellar/gettext/0.26
win+Meson test (3)
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.
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 (2)
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
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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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+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 (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+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+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 (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 (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 (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 (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 (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 (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 (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.4 KB
sha256:a3ae31152ed94d6a4bb309ce135fa0a27db61683c032eafeefd8c6d983a8315b
failed-tests-linux-breaking-changes
33.1 KB
sha256:23f753540ed7548df74c77cb3e20b7224e0c204275f43b9aa81bec9c3eb14640
failed-tests-linux-leaks
33.4 KB
sha256:1a7f8554b55770d5c5afbe41e497fd6a7a0572d2765049cda1c99cc7e1f53867
failed-tests-linux-meson
32.5 KB
sha256:fca1629c6d78e704a05c2b81db2494601cb2325b278f8aca7be21215134b615d
failed-tests-linux-reftable
33.5 KB
sha256:efedcf3b07b92c197ecd1790bc3d4a31c180efa1d1407a0f3ba9499991f499da
failed-tests-linux-reftable-leaks
33.6 KB
sha256:2edfc3b6332eb947fbdb007ed8ef2098588f0e7aa6e754237ecceca49e9e2528
failed-tests-linux-sha256
33.6 KB
sha256:d394aebf5924b0f17a77fe309bdc85edc3beb13e169d7f0038df6e68a66d6d63
failed-tests-osx-clang
32.3 KB
sha256:e0cb33b5baf646abd137b0fe4ac444fa42077c87e5dd28ff0314edaf449868b6
failed-tests-osx-gcc
32.3 KB
sha256:a3d486506f6af960817358997f29060c42cbdf35183aefc16fa0703fce261fcf
failed-tests-osx-meson
31.6 KB
sha256:602f3aca53cf7495f14d1810b2c00f56b35021132062b70cf96ccfc723a29fd2
failed-tests-osx-reftable
32.4 KB
sha256:be33bd6396e5e99f1b848e66de11c564924aeae4e4f029fa44c4dbbfc64b15db
failed-tests-windows-5
31.4 KB
sha256:6309f6d9071f41afe00b4c84f3155db36a54e8e1b6a4b52e03d39e7255e5e532
failed-tests-windows-vs-5
31.9 KB
sha256:7508791be6faf34baeda3b50855fadcafea567f5909d5d11203cf0839e272977
vs-artifacts-arm64
27.8 MB
sha256:b05d1da0fc5b11af3ac065015863acff2caa5de396f834c75a4119c3c5c1fb71
vs-artifacts-x64
28.8 MB
sha256:30b92af00c2e632f9706ce41da201f189ea272a9fac40d2e3c7b8b724a52eb48
windows-artifacts
98.9 MB
sha256:737d6cd5b529f780b0a0738e95ce4ccbcaf5e95fa1081029c4c8e582062b5885
windows-meson-artifacts
35.5 MB
sha256:b67da4da85769e00b8539a8500013aa3ef56eb795698f3aae65bc3a791dbacb1