odb: add write_packfile, for_each_unique_abbrev, convert_object_id #27084
MayCXCmain.yml
on: pull_request
config
7s
fuzz smoke test
1m 13s
static-analysis
5m 27s
rust-analysis
1m 34s
sparse
3m 33s
documentation
8m 1s
Matrix: dockerized
Matrix: regular
Matrix: win+VS test
Matrix: win+Meson test
Matrix: win test
Annotations
317 errors and 86 warnings
|
linux32 (i386/ubuntu:focal)
Process completed with exit code 2.
|
|
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: t5310.207 pack-objects respects --local (non-local pack)
|
|
linux32 (i386/ubuntu:focal)
failed: t5310.126 pack-objects respects --local (non-local pack)
|
|
linux32 (i386/ubuntu:focal)
failed: t5310.50 pack-objects respects --local (non-local pack)
|
|
linux32 (i386/ubuntu:focal)
failed: t5300.55 prefetch objects
|
|
linux32 (i386/ubuntu:focal)
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: 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: t5310.207 pack-objects respects --local (non-local pack)
|
|
linux-musl-meson (alpine:latest)
failed: t5310.126 pack-objects respects --local (non-local pack)
|
|
linux-musl-meson (alpine:latest)
failed: t5310.50 pack-objects respects --local (non-local pack)
|
|
linux-musl-meson (alpine:latest)
failed: t5300.55 prefetch objects
|
|
linux-musl-meson (alpine:latest)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
almalinux-8 (almalinux:8)
Process completed with exit code 1.
|
|
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: t5310.207 pack-objects respects --local (non-local pack)
|
|
almalinux-8 (almalinux:8)
failed: t5310.126 pack-objects respects --local (non-local pack)
|
|
almalinux-8 (almalinux:8)
failed: t5310.50 pack-objects respects --local (non-local pack)
|
|
almalinux-8 (almalinux:8)
failed: t5300.55 prefetch objects
|
|
almalinux-8 (almalinux:8)
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: 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: t5310.207 pack-objects respects --local (non-local pack)
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t5310.126 pack-objects respects --local (non-local pack)
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t5310.50 pack-objects respects --local (non-local pack)
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t5300.55 prefetch objects
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
debian-11 (debian:11)
Process completed with exit code 2.
|
|
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: t5310.207 pack-objects respects --local (non-local pack)
|
|
debian-11 (debian:11)
failed: t5310.126 pack-objects respects --local (non-local pack)
|
|
debian-11 (debian:11)
failed: t5310.50 pack-objects respects --local (non-local pack)
|
|
debian-11 (debian:11)
failed: t5300.55 prefetch objects
|
|
debian-11 (debian:11)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
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: t5310.207 pack-objects respects --local (non-local pack)
|
|
linux-meson (ubuntu:rolling)
failed: t5310.126 pack-objects respects --local (non-local pack)
|
|
linux-meson (ubuntu:rolling)
failed: t5310.50 pack-objects respects --local (non-local pack)
|
|
linux-meson (ubuntu:rolling)
failed: t5300.55 prefetch objects
|
|
linux-meson (ubuntu:rolling)
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: 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: t5310.207 pack-objects respects --local (non-local pack)
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5310.126 pack-objects respects --local (non-local pack)
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5310.50 pack-objects respects --local (non-local pack)
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5300.55 prefetch objects
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
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: t5310.207 pack-objects respects --local (non-local pack)
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5310.126 pack-objects respects --local (non-local pack)
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5310.50 pack-objects respects --local (non-local pack)
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5300.55 prefetch objects
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
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: t5310.207 pack-objects respects --local (non-local pack)
|
|
linux-sha256 (ubuntu:rolling)
failed: t5310.126 pack-objects respects --local (non-local pack)
|
|
linux-sha256 (ubuntu:rolling)
failed: t5310.50 pack-objects respects --local (non-local pack)
|
|
linux-sha256 (ubuntu:rolling)
failed: t5300.55 prefetch objects
|
|
linux-sha256 (ubuntu:rolling)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
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: t5310.207 pack-objects respects --local (non-local pack)
|
|
linux-reftable (ubuntu:rolling)
failed: t5310.126 pack-objects respects --local (non-local pack)
|
|
linux-reftable (ubuntu:rolling)
failed: t5310.50 pack-objects respects --local (non-local pack)
|
|
linux-reftable (ubuntu:rolling)
failed: t5300.55 prefetch objects
|
|
linux-reftable (ubuntu:rolling)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
win test (5)
failed: t5329.19 cruft --local drops unreachable objects
|
|
win test (5)
failed: t5329.17 loose objects mtimes upsert others
|
|
win test (5)
failed: t5329.15 cruft trees rescue sub-trees, blobs
|
|
win test (5)
failed: t5329.14 cruft commits rescue parents, trees
|
|
win test (5)
failed: t5329.13 cruft tags rescue tagged objects
|
|
win test (5)
failed: t5329.9 unreachable cruft objects are repacked (expire 2.weeks.ago)
|
|
win test (5)
failed: t5329.8 unreachable packed objects are packed (expire 2.weeks.ago)
|
|
win test (5)
failed: t5329.3 unreachable cruft objects are repacked (expire never)
|
|
win test (5)
failed: t5329.2 unreachable packed objects are packed (expire never)
|
|
win test (5)
failed: t5300.55 prefetch objects
|
|
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: t6020.14 clone from bundle
|
|
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
|
|
win test (6)
Process completed with exit code 1.
|
|
win test (6)
failed: t7900.29 geometric repacking task
|
|
win test (7)
failed: t5331.11 --stdin-packs=follow walks into unknown packs
|
|
win test (7)
failed: t5331.10 pack-objects --stdin with packfiles from main and alternate object database
|
|
win test (7)
failed: t5331.9 pack-objects --stdin with packfiles from alternate object database
|
|
win test (7)
failed: t5331.7 pack-objects --stdin with duplicate packfile
|
|
win test (7)
failed: t5331.6 --stdin-packs with broken links
|
|
win test (7)
failed: t5331.5 --stdin-packs with loose objects
|
|
win test (7)
failed: t5331.2 --stdin-packs with excluded packs
|
|
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
|
|
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: t5310.207 pack-objects respects --local (non-local pack)
|
|
osx-gcc (macos-14)
failed: t5310.126 pack-objects respects --local (non-local pack)
|
|
osx-gcc (macos-14)
failed: t5310.50 pack-objects respects --local (non-local pack)
|
|
osx-gcc (macos-14)
failed: t5300.55 prefetch objects
|
|
osx-gcc (macos-14)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
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: t5310.207 pack-objects respects --local (non-local pack)
|
|
osx-reftable (macos-14)
failed: t5310.126 pack-objects respects --local (non-local pack)
|
|
osx-reftable (macos-14)
failed: t5310.50 pack-objects respects --local (non-local pack)
|
|
osx-reftable (macos-14)
failed: t5300.55 prefetch objects
|
|
osx-reftable (macos-14)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
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
|
|
win test (4)
failed: t5310.207 pack-objects respects --local (non-local pack)
|
|
win test (4)
failed: t5310.126 pack-objects respects --local (non-local pack)
|
|
win test (4)
failed: t5310.50 pack-objects respects --local (non-local pack)
|
|
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: t5310.207 pack-objects respects --local (non-local pack)
|
|
osx-clang (macos-14)
failed: t5310.126 pack-objects respects --local (non-local pack)
|
|
osx-clang (macos-14)
failed: t5310.50 pack-objects respects --local (non-local pack)
|
|
osx-clang (macos-14)
failed: t5300.55 prefetch objects
|
|
osx-clang (macos-14)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
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.10 --geometric with pack.packSizeLimit
|
|
win test (1)
failed: t7703.9 --geometric chooses largest MIDX preferred pack
|
|
win test (1)
failed: t7703.7 --geometric ignores kept packs
|
|
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
|
|
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
|
|
win+Meson test (5)
failed: t7700.17 bitmaps can be disabled on bare repos
|
|
win+Meson test (5)
failed: t7700.16 incremental repack does not complain
|
|
win+Meson test (5)
failed: t7700.15 bitmaps are created by default in bare repos
|
|
win+Meson test (5)
failed: t7700.13 repack --keep-pack
|
|
win+Meson test (5)
failed: t7700.12 objects made unreachable by grafts only are kept
|
|
win+Meson test (5)
failed: t7700.11 local packed unreachable obs that exist in alternate ODB are not loosened
|
|
win+Meson test (5)
failed: t7700.10 packed unreachable obs in alternate ODB are not loosened
|
|
win+Meson test (5)
failed: t7700.9 packed obs in alternate ODB kept pack are repacked
|
|
win+Meson test (5)
failed: t7700.8 packed obs in alt ODB are repacked when local repo has packs
|
|
win+Meson test (5)
failed: t7700.7 packed obs in alt ODB are repacked even when local repo is packless
|
|
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
|
|
win+Meson test (2)
Process completed with exit code 1.
|
|
win+Meson test (2)
failed: t6500.7 gc --keep-largest-pack
|
|
win+Meson test (2)
failed: t5331.12 --stdin-packs with promisors
|
|
win+Meson test (2)
failed: t5331.11 --stdin-packs=follow walks into unknown packs
|
|
win+Meson test (2)
failed: t5331.10 pack-objects --stdin with packfiles from main and alternate object database
|
|
win+Meson test (2)
failed: t5331.9 pack-objects --stdin with packfiles from alternate object database
|
|
win+Meson test (2)
failed: t5331.7 pack-objects --stdin with duplicate packfile
|
|
win+Meson test (2)
failed: t5331.6 --stdin-packs with broken links
|
|
win+Meson test (2)
failed: t5331.5 --stdin-packs with loose objects
|
|
win+Meson test (2)
failed: t5331.2 --stdin-packs with excluded packs
|
|
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 (4)
failed: t6020.14 clone from bundle
|
|
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.10 --geometric with pack.packSizeLimit
|
|
win+Meson test (8)
failed: t7703.9 --geometric chooses largest MIDX preferred pack
|
|
win+Meson test (8)
failed: t7703.7 --geometric ignores kept packs
|
|
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 (0)
failed: t5329.22 gc.recentObjectsHook
|
|
win+Meson test (0)
failed: t5329.19 cruft --local drops unreachable objects
|
|
win+Meson test (0)
failed: t5329.17 loose objects mtimes upsert others
|
|
win+Meson test (0)
failed: t5329.15 cruft trees rescue sub-trees, blobs
|
|
win+Meson test (0)
failed: t5329.14 cruft commits rescue parents, trees
|
|
win+Meson test (0)
failed: t5329.13 cruft tags rescue tagged objects
|
|
win+Meson test (0)
failed: t5329.9 unreachable cruft objects are repacked (expire 2.weeks.ago)
|
|
win+Meson test (0)
failed: t5329.8 unreachable packed objects are packed (expire 2.weeks.ago)
|
|
win+Meson test (0)
failed: t5329.3 unreachable cruft objects are repacked (expire never)
|
|
win+Meson test (0)
failed: t5329.2 unreachable packed objects are packed (expire never)
|
|
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: t5310.207 pack-objects respects --local (non-local pack)
|
|
osx-meson (macos-14)
failed: t5310.126 pack-objects respects --local (non-local pack)
|
|
osx-meson (macos-14)
failed: t5310.50 pack-objects respects --local (non-local pack)
|
|
osx-meson (macos-14)
failed: t5300.55 prefetch objects
|
|
osx-meson (macos-14)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
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: t5310.207 pack-objects respects --local (non-local pack)
|
|
win+Meson test (1)
failed: t5310.126 pack-objects respects --local (non-local pack)
|
|
win+Meson test (1)
failed: t5310.50 pack-objects respects --local (non-local pack)
|
|
win+Meson test (1)
failed: t5300.55 prefetch objects
|
|
win+Meson test (1)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
win+Meson test (9)
failed: t7704.14 cruft packs are not included in geometric repack
|
|
win+Meson test (9)
failed: t7704.12 reachable packs are preferred over cruft ones
|
|
win+Meson test (9)
failed: t7704.10 --max-cruft-size with pruning
|
|
win+Meson test (9)
failed: t7704.9 multi-cruft with freshened objects (previously cruft)
|
|
win+Meson test (9)
failed: t7704.8 cruft with freshened objects (packed)
|
|
win+Meson test (9)
failed: t7704.7 cruft with freshened objects (loose)
|
|
win+Meson test (9)
failed: t7704.5 --combine-cruft-below-size combines packs
|
|
win+Meson test (9)
failed: t7704.4 --max-cruft-size combines existing packs when not too large
|
|
win+Meson test (9)
failed: t7704.3 --max-cruft-size creates new packs when too large
|
|
win+Meson test (9)
failed: t7704.2 --expire-to stores pruned objects (5.minutes.ago)
|
|
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-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: t5310.207 pack-objects respects --local (non-local pack)
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5310.126 pack-objects respects --local (non-local pack)
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5310.50 pack-objects respects --local (non-local pack)
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5300.55 prefetch objects
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
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: t5310.207 pack-objects respects --local (non-local pack)
|
|
linux-leaks (ubuntu:rolling)
failed: t5310.126 pack-objects respects --local (non-local pack)
|
|
linux-leaks (ubuntu:rolling)
failed: t5310.50 pack-objects respects --local (non-local pack)
|
|
linux-leaks (ubuntu:rolling)
failed: t5300.55 prefetch objects
|
|
linux-leaks (ubuntu:rolling)
failed: t1410.10 --stale-fix handles missing objects generously
|
|
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: t5310.207 pack-objects respects --local (non-local pack)
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5310.126 pack-objects respects --local (non-local pack)
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5310.50 pack-objects respects --local (non-local pack)
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5300.55 prefetch objects
|
|
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. 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 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/
|
|
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.
|
|
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
|
|
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. 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
|
|
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
|
|
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. 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/
|
|
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
|
|
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-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. 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-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-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 (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/
|
|
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/
|
|
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/
|
|
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/
|
|
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, 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 (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 (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 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 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@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 (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/
|
|
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
|
|
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 (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/
|
|
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 (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/
|
|
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/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 (5)
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 (5)
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 (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/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 (2)
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 (2)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
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 (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 (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@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 (0)
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 (0)
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
|
|
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 (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/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 (9)
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 (9)
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.
|
|
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. 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-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. 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-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
|
75.5 MB |
sha256:d1ec1ec5dccb1d46a1e4b4f3b19b05344b2688183087beb1ad20b5b695fbf53a
|
|
|
failed-tests-debian-11
|
75.5 MB |
sha256:34e32a7e72e652bb27f5957d76d685a1825c74c7ddd598dc647c3df28079cadc
|
|
|
failed-tests-fedora-breaking-changes-meson
|
75.5 MB |
sha256:f3b6ed6c94723967e8765bc37a720de89e2ca37aacaa34b111c7461c12ecb1ff
|
|
|
failed-tests-linux-TEST-vars
|
76 MB |
sha256:a91aa6334a1ab07ff14d881975c424930c77d8b9c0b115749f174c9f80d4bfea
|
|
|
failed-tests-linux-asan-ubsan
|
75.8 MB |
sha256:86dfb27d2fcb2209bcb3c427bbda9bc6f93be567103faec9bcdf1a085851f1b0
|
|
|
failed-tests-linux-breaking-changes
|
76.2 MB |
sha256:6188102605380575b870a5658363f0fb04c590431acaf8088838c45a02652efd
|
|
|
failed-tests-linux-leaks
|
75.8 MB |
sha256:ace05c8e8f84ea65a87a5afcbed0bb2a1e5546cac4ff8e0a5ae6051596bfc526
|
|
|
failed-tests-linux-meson
|
75.9 MB |
sha256:5981e6139c2510fe7b7daff03ec5836411f1d3029e9f12fe80f71ee8d7973d37
|
|
|
failed-tests-linux-musl-meson
|
75.7 MB |
sha256:c4565b793d9a71f8eab7245b62dd1fb21aaf074d2182168e88cf19e02778ed28
|
|
|
failed-tests-linux-reftable
|
75.9 MB |
sha256:dfa8a835905d2882b46f88d354ba0f326dc8373bd9f3ccde2e40ff9de0eb9ddb
|
|
|
failed-tests-linux-reftable-leaks
|
75.9 MB |
sha256:da2f344ffa5f19711dfab9463f24bdfab27c5a8d7dde1170b89d4db0de78b483
|
|
|
failed-tests-linux-sha256
|
76.2 MB |
sha256:71d6c459746cd62e33a311e49a8e7ff4d8625fc9231e4a44a6cc72f1a6504b3e
|
|
|
failed-tests-linux32
|
75.5 MB |
sha256:8bf0290fc7163c30726ce06684aa7f7e821cf5b2c793d9543c86d26ad940277e
|
|
|
failed-tests-osx-clang
|
75.4 MB |
sha256:b30f3c18c2e4a4c07058db5b101c1b546ddae430f2cb2e124dbda28988112636
|
|
|
failed-tests-osx-gcc
|
75.4 MB |
sha256:577e7d5b10513008a9f75b008649c745dff0cad538b4ea28bddf7f14ad50fe6f
|
|
|
failed-tests-osx-meson
|
75.5 MB |
sha256:6625c937651a742886cc337230a42c659383cf94bde38cecc5897645ee27b303
|
|
|
failed-tests-osx-reftable
|
75.5 MB |
sha256:b8fcc9cfb9b60a3212c6afae55f66b8cbce1833d4ce24fc8e8e5ae86cf2ddfd7
|
|
|
failed-tests-windows-0
|
729 KB |
sha256:05ac793d631f5e1e4fdc0719045454abd625f26a76565c5a6a4e23f689567dee
|
|
|
failed-tests-windows-1
|
4.2 MB |
sha256:c48af77200ac660e973e06aea21f8277683cd1d09e4e96ec343b6f3f2b4dda35
|
|
|
failed-tests-windows-4
|
4.02 MB |
sha256:72ee591610efeea416d402acddbe4e20e100f1e9a0bc6ee06c813efb0e7c4f6d
|
|
|
failed-tests-windows-5
|
56.2 MB |
sha256:82a0871c054de45717eb64494a7cf0e29f0b9ac26897f9761486cd41b8157a96
|
|
|
failed-tests-windows-6
|
205 KB |
sha256:44a8166093917ef13cdb1dc5feca2aa1016c1a6018c048cf82bdd3bc8f75000d
|
|
|
failed-tests-windows-7
|
9.95 MB |
sha256:7615be0533c6b9d1e27925ca06894e1ccb2ed1b8b57622cc0888b92c78d9eae7
|
|
|
windows-artifacts
|
96.8 MB |
sha256:99bebe4c73ce50fa2cf8d7cb852e4d913bd6fdfcd987436d90010688190d8262
|
|
|
windows-meson-artifacts
|
48.2 MB |
sha256:9973b89b1c3467a797cc13cb18b2ccb9ad73fef820d1938271833e771b865abf
|
|