odb: add write_packfile, for_each_unique_abbrev, convert_object_id #27079
MayCXCmain.yml
on: pull_request
config
7s
fuzz smoke test
1m 25s
static-analysis
5m 28s
rust-analysis
1m 43s
sparse
3m 24s
documentation
7m 31s
Matrix: dockerized
Matrix: regular
Matrix: win+VS test
Matrix: win+Meson test
Matrix: win test
Annotations
256 errors and 82 warnings
|
debian-11 (debian:11)
Process completed with exit code 2.
|
|
debian-11 (debian:11)
failed: t5801.10 fetch multiple branches
|
|
debian-11 (debian:11)
failed: t5801.9 fetch new branch
|
|
debian-11 (debian:11)
failed: t5801.8 pushing to local repo
|
|
debian-11 (debian:11)
failed: t5327.205 create multi-pack midx with bitmaps
|
|
debian-11 (debian:11)
failed: t5327.48 create multi-pack midx with bitmaps
|
|
debian-11 (debian:11)
failed: t5326.293 verify resulting bitmaps (MIDX -> pack)
|
|
debian-11 (debian:11)
failed: t5326.222 create multi-pack midx with bitmaps
|
|
debian-11 (debian:11)
failed: t5326.119 verify resulting bitmaps (MIDX -> pack)
|
|
debian-11 (debian:11)
failed: t5326.48 create multi-pack midx with bitmaps
|
|
debian-11 (debian:11)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
linux-musl-meson (alpine:latest)
Process completed with exit code 1.
|
|
linux-musl-meson (alpine:latest)
failed: t5801.10 fetch multiple branches
|
|
linux-musl-meson (alpine:latest)
failed: t5801.9 fetch new branch
|
|
linux-musl-meson (alpine:latest)
failed: t5801.8 pushing to local repo
|
|
linux-musl-meson (alpine:latest)
failed: t5327.205 create multi-pack midx with bitmaps
|
|
linux-musl-meson (alpine:latest)
failed: t5327.48 create multi-pack midx with bitmaps
|
|
linux-musl-meson (alpine:latest)
failed: t5326.293 verify resulting bitmaps (MIDX -> pack)
|
|
linux-musl-meson (alpine:latest)
failed: t5326.222 create multi-pack midx with bitmaps
|
|
linux-musl-meson (alpine:latest)
failed: t5326.119 verify resulting bitmaps (MIDX -> pack)
|
|
linux-musl-meson (alpine:latest)
failed: t5326.48 create multi-pack midx with bitmaps
|
|
linux-musl-meson (alpine:latest)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
fedora-breaking-changes-meson (fedora:latest)
Process completed with exit code 1.
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t5801.10 fetch multiple branches
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t5801.9 fetch new branch
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t5801.8 pushing to local repo
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t5327.205 create multi-pack midx with bitmaps
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t5327.48 create multi-pack midx with bitmaps
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t5326.293 verify resulting bitmaps (MIDX -> pack)
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t5326.222 create multi-pack midx with bitmaps
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t5326.119 verify resulting bitmaps (MIDX -> pack)
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t5326.48 create multi-pack midx with bitmaps
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
linux32 (i386/ubuntu:focal)
Process completed with exit code 2.
|
|
linux32 (i386/ubuntu:focal)
failed: t5801.10 fetch multiple branches
|
|
linux32 (i386/ubuntu:focal)
failed: t5801.9 fetch new branch
|
|
linux32 (i386/ubuntu:focal)
failed: t5801.8 pushing to local repo
|
|
linux32 (i386/ubuntu:focal)
failed: t5327.205 create multi-pack midx with bitmaps
|
|
linux32 (i386/ubuntu:focal)
failed: t5327.48 create multi-pack midx with bitmaps
|
|
linux32 (i386/ubuntu:focal)
failed: t5326.293 verify resulting bitmaps (MIDX -> pack)
|
|
linux32 (i386/ubuntu:focal)
failed: t5326.222 create multi-pack midx with bitmaps
|
|
linux32 (i386/ubuntu:focal)
failed: t5326.119 verify resulting bitmaps (MIDX -> pack)
|
|
linux32 (i386/ubuntu:focal)
failed: t5326.48 create multi-pack midx with bitmaps
|
|
linux32 (i386/ubuntu:focal)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
almalinux-8 (almalinux:8)
Process completed with exit code 1.
|
|
almalinux-8 (almalinux:8)
failed: t5801.10 fetch multiple branches
|
|
almalinux-8 (almalinux:8)
failed: t5801.9 fetch new branch
|
|
almalinux-8 (almalinux:8)
failed: t5801.8 pushing to local repo
|
|
almalinux-8 (almalinux:8)
failed: t5327.205 create multi-pack midx with bitmaps
|
|
almalinux-8 (almalinux:8)
failed: t5327.48 create multi-pack midx with bitmaps
|
|
almalinux-8 (almalinux:8)
failed: t5326.293 verify resulting bitmaps (MIDX -> pack)
|
|
almalinux-8 (almalinux:8)
failed: t5326.222 create multi-pack midx with bitmaps
|
|
almalinux-8 (almalinux:8)
failed: t5326.119 verify resulting bitmaps (MIDX -> pack)
|
|
almalinux-8 (almalinux:8)
failed: t5326.48 create multi-pack midx with bitmaps
|
|
almalinux-8 (almalinux:8)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
linux-TEST-vars (ubuntu:20.04)
Process completed with exit code 2.
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5801.10 fetch multiple branches
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5801.9 fetch new branch
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5801.8 pushing to local repo
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5327.205 create multi-pack midx with bitmaps
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5327.48 create multi-pack midx with bitmaps
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5326.293 verify resulting bitmaps (MIDX -> pack)
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5326.222 create multi-pack midx with bitmaps
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5326.119 verify resulting bitmaps (MIDX -> pack)
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5326.48 create multi-pack midx with bitmaps
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
linux-reftable (ubuntu:rolling)
failed: t5801.10 fetch multiple branches
|
|
linux-reftable (ubuntu:rolling)
failed: t5801.9 fetch new branch
|
|
linux-reftable (ubuntu:rolling)
failed: t5801.8 pushing to local repo
|
|
linux-reftable (ubuntu:rolling)
failed: t5327.205 create multi-pack midx with bitmaps
|
|
linux-reftable (ubuntu:rolling)
failed: t5327.48 create multi-pack midx with bitmaps
|
|
linux-reftable (ubuntu:rolling)
failed: t5326.293 verify resulting bitmaps (MIDX -> pack)
|
|
linux-reftable (ubuntu:rolling)
failed: t5326.222 create multi-pack midx with bitmaps
|
|
linux-reftable (ubuntu:rolling)
failed: t5326.119 verify resulting bitmaps (MIDX -> pack)
|
|
linux-reftable (ubuntu:rolling)
failed: t5326.48 create multi-pack midx with bitmaps
|
|
linux-reftable (ubuntu:rolling)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5801.10 fetch multiple branches
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5801.9 fetch new branch
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5801.8 pushing to local repo
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5327.205 create multi-pack midx with bitmaps
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5327.48 create multi-pack midx with bitmaps
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5326.293 verify resulting bitmaps (MIDX -> pack)
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5326.222 create multi-pack midx with bitmaps
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5326.119 verify resulting bitmaps (MIDX -> pack)
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5326.48 create multi-pack midx with bitmaps
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
linux-sha256 (ubuntu:rolling)
failed: t5801.10 fetch multiple branches
|
|
linux-sha256 (ubuntu:rolling)
failed: t5801.9 fetch new branch
|
|
linux-sha256 (ubuntu:rolling)
failed: t5801.8 pushing to local repo
|
|
linux-sha256 (ubuntu:rolling)
failed: t5327.205 create multi-pack midx with bitmaps
|
|
linux-sha256 (ubuntu:rolling)
failed: t5327.48 create multi-pack midx with bitmaps
|
|
linux-sha256 (ubuntu:rolling)
failed: t5326.293 verify resulting bitmaps (MIDX -> pack)
|
|
linux-sha256 (ubuntu:rolling)
failed: t5326.222 create multi-pack midx with bitmaps
|
|
linux-sha256 (ubuntu:rolling)
failed: t5326.119 verify resulting bitmaps (MIDX -> pack)
|
|
linux-sha256 (ubuntu:rolling)
failed: t5326.48 create multi-pack midx with bitmaps
|
|
linux-sha256 (ubuntu:rolling)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
linux-meson (ubuntu:rolling)
failed: t5801.10 fetch multiple branches
|
|
linux-meson (ubuntu:rolling)
failed: t5801.9 fetch new branch
|
|
linux-meson (ubuntu:rolling)
failed: t5801.8 pushing to local repo
|
|
linux-meson (ubuntu:rolling)
failed: t5327.205 create multi-pack midx with bitmaps
|
|
linux-meson (ubuntu:rolling)
failed: t5327.48 create multi-pack midx with bitmaps
|
|
linux-meson (ubuntu:rolling)
failed: t5326.293 verify resulting bitmaps (MIDX -> pack)
|
|
linux-meson (ubuntu:rolling)
failed: t5326.222 create multi-pack midx with bitmaps
|
|
linux-meson (ubuntu:rolling)
failed: t5326.119 verify resulting bitmaps (MIDX -> pack)
|
|
linux-meson (ubuntu:rolling)
failed: t5326.48 create multi-pack midx with bitmaps
|
|
linux-meson (ubuntu:rolling)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
win test (0)
Process completed with exit code 1.
|
|
win test (0)
failed: t9302.3 lookups after checkpoint works
|
|
win test (0)
failed: t9302.2 bigger packs are preserved
|
|
win test (0)
failed: t9302.1 create loose objects on import
|
|
win test (0)
failed: t5326.293 verify resulting bitmaps (MIDX -> pack)
|
|
win test (0)
failed: t5326.222 create multi-pack midx with bitmaps
|
|
win test (0)
failed: t5326.119 verify resulting bitmaps (MIDX -> pack)
|
|
win test (0)
failed: t5326.48 create multi-pack midx with bitmaps
|
|
osx-reftable (macos-14)
failed: t5801.10 fetch multiple branches
|
|
osx-reftable (macos-14)
failed: t5801.9 fetch new branch
|
|
osx-reftable (macos-14)
failed: t5801.8 pushing to local repo
|
|
osx-reftable (macos-14)
failed: t5327.205 create multi-pack midx with bitmaps
|
|
osx-reftable (macos-14)
failed: t5327.48 create multi-pack midx with bitmaps
|
|
osx-reftable (macos-14)
failed: t5326.293 verify resulting bitmaps (MIDX -> pack)
|
|
osx-reftable (macos-14)
failed: t5326.222 create multi-pack midx with bitmaps
|
|
osx-reftable (macos-14)
failed: t5326.119 verify resulting bitmaps (MIDX -> pack)
|
|
osx-reftable (macos-14)
failed: t5326.48 create multi-pack midx with bitmaps
|
|
osx-reftable (macos-14)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
win test (1)
failed: t9300.61 I: verify edge list
|
|
win test (1)
failed: t9300.25 B: accept and fixup committer with no name
|
|
win test (1)
failed: t9300.22 B: accept empty committer
|
|
win test (1)
failed: t7703.18 geometric repack works with promisor packs
|
|
win test (1)
failed: t7703.17 --geometric -l disables writing bitmaps with non-local packfiles
|
|
win test (1)
failed: t7703.16 --geometric -l with non-intact geometric sequence across ODBs
|
|
win test (1)
failed: t7703.9 --geometric chooses largest MIDX preferred pack
|
|
win test (1)
failed: t7703.6 --geometric with small- and large-pack rollup
|
|
win test (1)
failed: t7703.5 --geometric with small-pack rollup
|
|
win test (1)
failed: t7703.4 --geometric with loose objects
|
|
osx-clang (macos-14)
failed: t5801.10 fetch multiple branches
|
|
osx-clang (macos-14)
failed: t5801.9 fetch new branch
|
|
osx-clang (macos-14)
failed: t5801.8 pushing to local repo
|
|
osx-clang (macos-14)
failed: t5327.205 create multi-pack midx with bitmaps
|
|
osx-clang (macos-14)
failed: t5327.48 create multi-pack midx with bitmaps
|
|
osx-clang (macos-14)
failed: t5326.293 verify resulting bitmaps (MIDX -> pack)
|
|
osx-clang (macos-14)
failed: t5326.222 create multi-pack midx with bitmaps
|
|
osx-clang (macos-14)
failed: t5326.119 verify resulting bitmaps (MIDX -> pack)
|
|
osx-clang (macos-14)
failed: t5326.48 create multi-pack midx with bitmaps
|
|
osx-clang (macos-14)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
win test (7)
Process completed with exit code 1.
|
|
win test (7)
failed: t5327.205 create multi-pack midx with bitmaps
|
|
win test (7)
failed: t5327.48 create multi-pack midx with bitmaps
|
|
win test (7)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
win test (4)
failed: t5801.30 proper failure checks for pushing
|
|
win test (4)
failed: t5801.28 push update refs failure
|
|
win test (4)
failed: t5801.27 push update refs disabled by no-private-update
|
|
win test (4)
failed: t5801.26 push update refs
|
|
win test (4)
failed: t5801.16 forced push
|
|
win test (4)
failed: t5801.12 push new branch by name
|
|
win test (4)
failed: t5801.11 push when remote has extra refs
|
|
win test (4)
failed: t5801.10 fetch multiple branches
|
|
win test (4)
failed: t5801.9 fetch new branch
|
|
win test (4)
failed: t5801.8 pushing to local repo
|
|
osx-gcc (macos-14)
failed: t5801.10 fetch multiple branches
|
|
osx-gcc (macos-14)
failed: t5801.9 fetch new branch
|
|
osx-gcc (macos-14)
failed: t5801.8 pushing to local repo
|
|
osx-gcc (macos-14)
failed: t5327.205 create multi-pack midx with bitmaps
|
|
osx-gcc (macos-14)
failed: t5327.48 create multi-pack midx with bitmaps
|
|
osx-gcc (macos-14)
failed: t5326.293 verify resulting bitmaps (MIDX -> pack)
|
|
osx-gcc (macos-14)
failed: t5326.222 create multi-pack midx with bitmaps
|
|
osx-gcc (macos-14)
failed: t5326.119 verify resulting bitmaps (MIDX -> pack)
|
|
osx-gcc (macos-14)
failed: t5326.48 create multi-pack midx with bitmaps
|
|
osx-gcc (macos-14)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
win+Meson test (1)
Process completed with exit code 1.
|
|
win+Meson test (1)
failed: t9300.187 S: paths at EOL with octal escapes must work
|
|
win+Meson test (1)
failed: t9300.185 S: paths at EOL with quoted spaces must work
|
|
win+Meson test (1)
failed: t9300.154 R: print two blobs to stdout
|
|
win+Meson test (1)
failed: t9300.99 O: blank lines not necessary after other commands
|
|
win+Meson test (1)
failed: t9300.61 I: verify edge list
|
|
win+Meson test (1)
failed: t9300.25 B: accept and fixup committer with no name
|
|
win+Meson test (1)
failed: t9300.22 B: accept empty committer
|
|
win+Meson test (1)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
win+Meson test (3)
Process completed with exit code 1.
|
|
win+Meson test (3)
failed: t9302.3 lookups after checkpoint works
|
|
win+Meson test (3)
failed: t9302.2 bigger packs are preserved
|
|
win+Meson test (3)
failed: t9302.1 create loose objects on import
|
|
osx-meson (macos-14)
failed: t5801.10 fetch multiple branches
|
|
osx-meson (macos-14)
failed: t5801.9 fetch new branch
|
|
osx-meson (macos-14)
failed: t5801.8 pushing to local repo
|
|
osx-meson (macos-14)
failed: t5327.205 create multi-pack midx with bitmaps
|
|
osx-meson (macos-14)
failed: t5327.48 create multi-pack midx with bitmaps
|
|
osx-meson (macos-14)
failed: t5326.293 verify resulting bitmaps (MIDX -> pack)
|
|
osx-meson (macos-14)
failed: t5326.222 create multi-pack midx with bitmaps
|
|
osx-meson (macos-14)
failed: t5326.119 verify resulting bitmaps (MIDX -> pack)
|
|
osx-meson (macos-14)
failed: t5326.48 create multi-pack midx with bitmaps
|
|
osx-meson (macos-14)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
linux-leaks (ubuntu:rolling)
failed: t5801.10 fetch multiple branches
|
|
linux-leaks (ubuntu:rolling)
failed: t5801.9 fetch new branch
|
|
linux-leaks (ubuntu:rolling)
failed: t5801.8 pushing to local repo
|
|
linux-leaks (ubuntu:rolling)
failed: t5327.205 create multi-pack midx with bitmaps
|
|
linux-leaks (ubuntu:rolling)
failed: t5327.48 create multi-pack midx with bitmaps
|
|
linux-leaks (ubuntu:rolling)
failed: t5326.293 verify resulting bitmaps (MIDX -> pack)
|
|
linux-leaks (ubuntu:rolling)
failed: t5326.222 create multi-pack midx with bitmaps
|
|
linux-leaks (ubuntu:rolling)
failed: t5326.119 verify resulting bitmaps (MIDX -> pack)
|
|
linux-leaks (ubuntu:rolling)
failed: t5326.48 create multi-pack midx with bitmaps
|
|
linux-leaks (ubuntu:rolling)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
win+Meson test (8)
Process completed with exit code 1.
|
|
win+Meson test (8)
failed: t7703.18 geometric repack works with promisor packs
|
|
win+Meson test (8)
failed: t7703.17 --geometric -l disables writing bitmaps with non-local packfiles
|
|
win+Meson test (8)
failed: t7703.16 --geometric -l with non-intact geometric sequence across ODBs
|
|
win+Meson test (8)
failed: t7703.9 --geometric chooses largest MIDX preferred pack
|
|
win+Meson test (8)
failed: t7703.6 --geometric with small- and large-pack rollup
|
|
win+Meson test (8)
failed: t7703.5 --geometric with small-pack rollup
|
|
win+Meson test (8)
failed: t7703.4 --geometric with loose objects
|
|
win+Meson test (8)
failed: t5327.205 create multi-pack midx with bitmaps
|
|
win+Meson test (8)
failed: t5327.48 create multi-pack midx with bitmaps
|
|
win+Meson test (7)
Process completed with exit code 1.
|
|
win+Meson test (7)
failed: t9306.10 import SSH signed tag with --signed-tags=strip
|
|
win+Meson test (7)
failed: t5326.293 verify resulting bitmaps (MIDX -> pack)
|
|
win+Meson test (7)
failed: t5326.222 create multi-pack midx with bitmaps
|
|
win+Meson test (7)
failed: t5326.119 verify resulting bitmaps (MIDX -> pack)
|
|
win+Meson test (7)
failed: t5326.48 create multi-pack midx with bitmaps
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5801.10 fetch multiple branches
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5801.9 fetch new branch
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5801.8 pushing to local repo
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5327.205 create multi-pack midx with bitmaps
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5327.48 create multi-pack midx with bitmaps
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5326.293 verify resulting bitmaps (MIDX -> pack)
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5326.222 create multi-pack midx with bitmaps
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5326.119 verify resulting bitmaps (MIDX -> pack)
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5326.48 create multi-pack midx with bitmaps
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
win+Meson test (4)
Process completed with exit code 1.
|
|
win+Meson test (4)
failed: t9303.16 fast-import (loose) with -c core.loosecompression=9
|
|
win+Meson test (4)
failed: t9303.15 fast-import (loose) with -c core.loosecompression=0
|
|
win+Meson test (4)
failed: t9303.14 fast-import (loose) with -c core.compression=9 -c core.loosecompression=9
|
|
win+Meson test (4)
failed: t9303.13 fast-import (loose) with -c core.compression=0 -c core.loosecompression=9
|
|
win+Meson test (4)
failed: t9303.12 fast-import (loose) with -c core.compression=9 -c core.loosecompression=0
|
|
win+Meson test (4)
failed: t9303.11 fast-import (loose) with -c core.compression=0 -c core.loosecompression=0
|
|
win+Meson test (4)
failed: t9303.10 fast-import (loose) with -c core.compression=9
|
|
win+Meson test (4)
failed: t9303.9 fast-import (loose) with -c core.compression=0
|
|
win+Meson test (6)
failed: t5801.30 proper failure checks for pushing
|
|
win+Meson test (6)
failed: t5801.28 push update refs failure
|
|
win+Meson test (6)
failed: t5801.27 push update refs disabled by no-private-update
|
|
win+Meson test (6)
failed: t5801.26 push update refs
|
|
win+Meson test (6)
failed: t5801.16 forced push
|
|
win+Meson test (6)
failed: t5801.12 push new branch by name
|
|
win+Meson test (6)
failed: t5801.11 push when remote has extra refs
|
|
win+Meson test (6)
failed: t5801.10 fetch multiple branches
|
|
win+Meson test (6)
failed: t5801.9 fetch new branch
|
|
win+Meson test (6)
failed: t5801.8 pushing to local repo
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5801.10 fetch multiple branches
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5801.9 fetch new branch
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5801.8 pushing to local repo
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5327.205 create multi-pack midx with bitmaps
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5327.48 create multi-pack midx with bitmaps
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5326.293 verify resulting bitmaps (MIDX -> pack)
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5326.222 create multi-pack midx with bitmaps
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5326.119 verify resulting bitmaps (MIDX -> pack)
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5326.48 create multi-pack midx with bitmaps
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
rust-analysis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
debian-11 (debian:11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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
|
|
linux-musl-meson (alpine:latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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
|
|
fedora-breaking-changes-meson (fedora:latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
fedora-breaking-changes-meson (fedora:latest)
JGit wasn't installed, see above for clues why
|
|
fedora-breaking-changes-meson (fedora:latest)
git-lfs wasn't installed, see above for clues why
|
|
fedora-breaking-changes-meson (fedora:latest)
perforce wasn't installed, see above for clues why
|
|
linux32 (i386/ubuntu:focal)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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
|
|
linux-TEST-vars (ubuntu:20.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-reftable (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-breaking-changes (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win test (5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-sha256 (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-meson (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win test (0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v5, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson build
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win test (6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win test (8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
osx-reftable (macos-14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
osx-reftable (macos-14)
JGit wasn't installed, see above for clues why
|
|
osx-reftable (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
|
|
win test (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v5, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
osx-clang (macos-14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
osx-clang (macos-14)
JGit wasn't installed, see above for clues why
|
|
osx-clang (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
|
|
win test (7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v5, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win test (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v5, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win test (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
osx-gcc (macos-14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
osx-gcc (macos-14)
JGit wasn't installed, see above for clues why
|
|
osx-gcc (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
|
|
win test (9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win test (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (1)
No files were found with the provided path: /d/a/git/git/build/test-output/failed-test-artifacts. No artifacts will be uploaded.
|
|
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)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (3)
No files were found with the provided path: /d/a/git/git/build/test-output/failed-test-artifacts. No artifacts will be uploaded.
|
|
win+Meson test (3)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (9)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
osx-meson (macos-14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
osx-meson (macos-14)
JGit wasn't installed, see above for clues why
|
|
osx-meson (macos-14)
pcre2 10.47_1 is already installed and up-to-date.
To reinstall 10.47_1, run:
brew reinstall pcre2
|
|
osx-meson (macos-14)
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
osx-meson (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
|
|
linux-leaks (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (8)
No files were found with the provided path: /d/a/git/git/build/test-output/failed-test-artifacts. No artifacts will be uploaded.
|
|
win+Meson test (8)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (7)
No files were found with the provided path: /d/a/git/git/build/test-output/failed-test-artifacts. No artifacts will be uploaded.
|
|
win+Meson test (7)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (5)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
linux-reftable-leaks (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (4)
No files were found with the provided path: /d/a/git/git/build/test-output/failed-test-artifacts. No artifacts will be uploaded.
|
|
win+Meson test (4)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (6)
No files were found with the provided path: /d/a/git/git/build/test-output/failed-test-artifacts. No artifacts will be uploaded.
|
|
win+Meson test (6)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (0)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
linux-asan-ubsan (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
failed-tests-almalinux-8
|
5.58 MB |
sha256:6b2be1c2176ae037d83f9262d2d1ace11e0efac98d937b54ace161c4b0664fe1
|
|
|
failed-tests-debian-11
|
5.57 MB |
sha256:f62071295493c436e2571d00ae675369053f3192ea12833ab54da96b48a1ea58
|
|
|
failed-tests-fedora-breaking-changes-meson
|
5.56 MB |
sha256:ece907c0a3d34a74093c55754b3af9f76ca87e5c46fd094b473d4bdc108e77ba
|
|
|
failed-tests-linux-TEST-vars
|
5.67 MB |
sha256:2e40a81b04e6c39cee2b2829dbd64596883be760c069997c9068c6567b8f0d8d
|
|
|
failed-tests-linux-asan-ubsan
|
5.59 MB |
sha256:333c7e7bec3bee4e8bf0671885bc81bd27789b7e80cced79a7175d79db5f3909
|
|
|
failed-tests-linux-breaking-changes
|
5.94 MB |
sha256:a66835dbc127bb653026deff78eb15e185af50870bf75c3993533be3ad61e720
|
|
|
failed-tests-linux-leaks
|
5.58 MB |
sha256:7440ef7215a36dde741b625f91039575fd258a11f374219c7d0da6734127d13f
|
|
|
failed-tests-linux-meson
|
5.63 MB |
sha256:9e579f97989497eb949714b26e1952dedaa4bc68b61060b9a2e3d075e6212faa
|
|
|
failed-tests-linux-musl-meson
|
5.57 MB |
sha256:b40d04eea6f25fe68f455ba2a7352f4cfa4b2877a7244b91634723d618eab3e1
|
|
|
failed-tests-linux-reftable
|
5.61 MB |
sha256:cf77eeecac9dd213cd13d0042c2c5a45414683d2cbb90c9c0b35f26327ccca57
|
|
|
failed-tests-linux-reftable-leaks
|
5.61 MB |
sha256:5dd584d83a0c8cf5ef315b9ea6aa1106550dd36edf1643198badb0e192c9a389
|
|
|
failed-tests-linux-sha256
|
5.93 MB |
sha256:57c991aa1cbb326a8a1bb1597ca9e03183e063a63f2dd0887a9d7f9948ef0705
|
|
|
failed-tests-linux32
|
5.58 MB |
sha256:adeb11d69c468f6c8078e57f5334f0d34cf31fd4a2a9b1041d082109f16936c1
|
|
|
failed-tests-osx-clang
|
5.56 MB |
sha256:77fabcf52785c23fee224e97e5ed2b15900d8e70ccdb64e419a7799ecd44b606
|
|
|
failed-tests-osx-gcc
|
5.57 MB |
sha256:806b36d1614efd5ce6eb010e5a1be025eef7b1357f74f832b2f9e5d3ec167ef0
|
|
|
failed-tests-osx-meson
|
5.58 MB |
sha256:000d1bd8f891b54b01ae03c40ae3dd9efbf99e289af4c436c9e3c309a2d89a82
|
|
|
failed-tests-osx-reftable
|
5.57 MB |
sha256:fc92ff4228a88491adcd33cc7d2169f46cb3159bbbd729941e627243c370dcfa
|
|
|
failed-tests-windows-0
|
642 KB |
sha256:4c0be98057fb5092ed6b1937ba23169a6eea4a1734bb94e2bccf03ea85ac9244
|
|
|
failed-tests-windows-1
|
4.2 MB |
sha256:3c59e946d16b5bc6ee2b5d80ab78ed869ec199b31ae12709b0a1a38dd7a2138b
|
|
|
failed-tests-windows-4
|
121 KB |
sha256:d7414e0816154d10ef54ee5b8ec45362dbf1981aca042889e8fcd1ed0fa4c2e2
|
|
|
failed-tests-windows-7
|
518 KB |
sha256:cd246b6806bf8a2d882d92c25e95647abccbc5ac2310594144e37b06e73a3c05
|
|
|
windows-artifacts
|
96.7 MB |
sha256:51bc2458ca6f85f05cbca8fab9eed1ff1b33d5e3d2265c0647a9e3d98c2fc6f0
|
|
|
windows-meson-artifacts
|
48.2 MB |
sha256:07d3f04b822c96b512eedbddfeaee6c52612c1a72cb9f5794a4bb4d3bf557d13
|
|