Skip to content

t: add test for git refs exists subcommand #46

t: add test for git refs exists subcommand

t: add test for git refs exists subcommand #46

Triggered via push August 22, 2025 08:36
Status Failure
Total duration 45m 47s
Artifacts 12

main.yml

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

24 errors, 36 warnings, and 22 notices
debian-11 (debian:11)
Process completed with exit code 2.
almalinux-8 (almalinux:8)
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: t0450.497 refs -h output and SYNOPSIS agree
linux-sha256 (ubuntu:rolling)
Process completed with exit code 1.
linux-sha256 (ubuntu:rolling)
failed: t0450.502 refs -h output and SYNOPSIS agree
win test (5)
Process completed with exit code 1.
win test (5)
failed: t0450.502 refs -h output and SYNOPSIS agree
linux-reftable (ubuntu:rolling)
Process completed with exit code 1.
linux-reftable (ubuntu:rolling)
failed: t0450.502 refs -h output and SYNOPSIS agree
linux-TEST-vars (ubuntu:20.04)
Process completed with exit code 2.
osx-gcc (macos-13)
Process completed with exit code 1.
osx-gcc (macos-13)
failed: t0450.502 refs -h output and SYNOPSIS agree
linux-leaks (ubuntu:rolling)
Process completed with exit code 1.
linux-leaks (ubuntu:rolling)
failed: t0450.502 refs -h output and SYNOPSIS agree
linux-asan-ubsan (ubuntu:rolling)
Process completed with exit code 1.
linux-asan-ubsan (ubuntu:rolling)
failed: t0450.502 refs -h output and SYNOPSIS agree
linux-reftable-leaks (ubuntu:rolling)
Process completed with exit code 1.
linux-reftable-leaks (ubuntu:rolling)
failed: t0450.502 refs -h output and SYNOPSIS agree
osx-reftable (macos-13)
Process completed with exit code 1.
osx-reftable (macos-13)
failed: t0450.502 refs -h output and SYNOPSIS agree
osx-clang (macos-13)
Process completed with exit code 1.
osx-clang (macos-13)
failed: t0450.502 refs -h output and SYNOPSIS agree
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.
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
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
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 (6)
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 (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 (1)
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 (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 (8)
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-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-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-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 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 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 (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 (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 (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
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 (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 (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 (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 (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 (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+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 (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 (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 (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 (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 Expired
105 KB
sha256:36a991f959f02e9543b50c27c5ac30cb9e3d0339ca1fb019c4545a594443836f
failed-tests-linux-breaking-changes Expired
104 KB
sha256:af222d72a0444897df9d70a8e92a73c2bdb18c16a50ad8e08832441307bf196b
failed-tests-linux-leaks Expired
105 KB
sha256:59058394b6854110397d26164cb06a8ea8fc85b7703f5923df158f4bebef680d
failed-tests-linux-reftable Expired
105 KB
sha256:5deb76e20eb5fa92d4f11d3250c9b950f37fc4929c8e6dab8d398995aee26654
failed-tests-linux-reftable-leaks Expired
105 KB
sha256:5aa23b1fc53cdb7370e7197aaba731dab22eb4f3cadae852db133fa93e015617
failed-tests-linux-sha256 Expired
105 KB
sha256:cbba636233b571e2a452170ac55d0170e7a8801dd5ecd5b3c45ff2ac1dde2dae
failed-tests-osx-clang Expired
105 KB
sha256:5706cec93f8b582508f108cdb030f5c89e1721bb3369638e14cc2306d4999702
failed-tests-osx-gcc Expired
105 KB
sha256:3b8ea788c8a29e1d45d09bf3f60943242361fcc79ef81cdd946763061cd6678e
failed-tests-osx-reftable Expired
105 KB
sha256:14bbc7fcac0cb94221fc77290a6e60b64039675bf007d6b7d0cc770218337975
failed-tests-windows-5 Expired
104 KB
sha256:9373df553c7626dd2e67cbc037b2162cc2531146cdb5873276db0eec055d37a4
windows-artifacts Expired
93.6 MB
sha256:8467434b2110a24c9f2fdd05dcf86383bd19255b4420b85e4d30e67f860c8aff
windows-meson-artifacts Expired
35 MB
sha256:ff1740732868584dcc7af66181da33bcf11648ef63414a6a41bea07c567ca6de