Skip to content

Merge 'readme' into HEAD #5859

Merge 'readme' into HEAD

Merge 'readme' into HEAD #5859

Triggered via push August 11, 2025 23:59
Status Failure
Total duration 41m 0s
Artifacts 17

main.yml

on: push
Matrix: win+VS build
win+Meson build
3m 34s
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

46 errors, 40 warnings, and 34 notices
documentation
Process completed with exit code 2.
linux-musl-meson (alpine:latest)
Process completed with exit code 1.
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-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
almalinux-8 (almalinux:8)
Process completed with exit code 1.
debian-11 (debian:11)
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-TEST-vars (ubuntu:20.04)
Process completed with exit code 2.
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
win+Meson test (8)
Process completed with exit code 1.
win+VS test (1)
Process completed with exit code 1.
win+VS test (1)
failed: t1517.352 'git survey --help-all' outside a repository
win+VS test (1)
failed: t1517.351 'git survey -h' outside a repository
win test (1)
Process completed with exit code 1.
win test (1)
failed: t1517.352 'git survey --help-all' outside a repository
win test (1)
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
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
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-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
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
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>0M4SaaAAAAAD9kukwtv6dRoRIyVqdZRcWQkwyQUEyMDMwMTA3MDIxAEVkZ2U=
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>0OYSaaAAAAABUEnkScjqMSofUC4NZ7WWuQlkzRURHRTA1MTMARWRnZQ==
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
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 (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.
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 (7)
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 (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 (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
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+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 (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 (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 (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 (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+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 (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 (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 (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 (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+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 (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 (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 (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 (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+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 (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 (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 (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 (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 (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 (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
failed-tests-linux-asan-ubsan Expired
33.6 KB
sha256:c445baf9a45a8116182fac22c9ead63286b38be9bc07196b6a39c1d1d14cfead
failed-tests-linux-breaking-changes Expired
33.3 KB
sha256:d95f95a01285092bf8594a47375ddc34bb26716a7cdd59e4d752104efe874f29
failed-tests-linux-leaks Expired
33.5 KB
sha256:79495fedb07ac60be38b360f6c9edfe46401572fb63e8cdd471b76bd371617ae
failed-tests-linux-meson Expired
32.7 KB
sha256:76a158e57d53ae5c65b772f77cd4a5d075bc179940bf793f0657b11e042f9e5d
failed-tests-linux-reftable Expired
33.7 KB
sha256:04d3ccfa0a73cfb79ffe72d73f59a4367dbe0423264a4486a2c8542affd9ae77
failed-tests-linux-reftable-leaks Expired
33.8 KB
sha256:6ac153276a3712cc5600222730072bb0d4676e49e4f1cb951bbbe59dc2b08a1d
failed-tests-linux-sha256 Expired
33.7 KB
sha256:71c0b7f94659c0689204a52bfd5313b4f87100e68e80968eb17a3d47401ff489
failed-tests-osx-clang Expired
32.5 KB
sha256:4b867d1e5286b9e7ad21b4b9667d008ef423b2455d6a054a5e04274c43210714
failed-tests-osx-gcc Expired
32.4 KB
sha256:69e7de492e5e0c287f4088db54d4d130e1c6619a3100e4af0b2f368a1ad82786
failed-tests-osx-meson Expired
31.8 KB
sha256:0e2970ddc14bdf3abf48961d2c99be4bc41e36dcd700ff1c9846e1e0349742d6
failed-tests-osx-reftable Expired
32.7 KB
sha256:9d1129128409fd19b246b1815b39997371a69edee7a585604d305132a9a942b6
failed-tests-windows-1 Expired
31.6 KB
sha256:1fca836790535ab2c0cf7888690299bfaa7f4514a3e844e574dbb24c00de5003
failed-tests-windows-vs-1 Expired
32.2 KB
sha256:e03fa6daa7ab133be572c9d029739216122282e901b99e625bbc584b273d015e
vs-artifacts-arm64 Expired
27.8 MB
sha256:aeb1d3e75e62f76a8b01bbc724987f076453035552fcd4594ec22ea22b4c02b7
vs-artifacts-x64 Expired
28.8 MB
sha256:fb9bde95379a84ec04c076ea61e7c4fa312ef98f194d0f00e18b31a49f37da85
windows-artifacts Expired
99 MB
sha256:ea62acc18a95f4409c124e5f3d7f9d0390c8a767e76268a97fda69ad76e68732
windows-meson-artifacts Expired
35.5 MB
sha256:3b060eec09e56df487c16fa6eae8de32b65140b81b5defdf078bc2eee7fd1bff