Skip to content

Merge branch 'wip/ci-only-two-leaks' into HEAD #27325

Merge branch 'wip/ci-only-two-leaks' into HEAD

Merge branch 'wip/ci-only-two-leaks' into HEAD #27325

Triggered via push April 10, 2026 22:41
Status Failure
Total duration 2m 40s
Artifacts 2

main.yml

on: push
Matrix: dockerized
Fit to window
Zoom out
Zoom in

Annotations

20 errors and 2 warnings
linux-leaks (ubuntu:rolling)
failed: t0410.35 promisor.quiet=false shows progress messages
linux-leaks (ubuntu:rolling)
failed: t0410.34 setup for promisor.quiet tests
linux-leaks (ubuntu:rolling)
failed: t0410.33 push should not fetch new commit objects
linux-leaks (ubuntu:rolling)
failed: t0410.32 lazy-fetch when accessing object not in the_repository
linux-leaks (ubuntu:rolling)
failed: t0410.31 exact rename does not need to fetch the blob lazily
linux-leaks (ubuntu:rolling)
failed: t0410.30 do not fetch when checking existence of tree we construct ourselves
linux-leaks (ubuntu:rolling)
failed: t0410.29 gc stops traversal when a missing but promised object is reached
linux-leaks (ubuntu:rolling)
failed: t0410.28 repack -d does not irreversibly delete promisor objects
linux-leaks (ubuntu:rolling)
failed: t0410.27 gc does not repack promisor objects if there are none
linux-leaks (ubuntu:rolling)
failed: t0410.26 gc repacks promisor objects separately from non-promisor objects
linux-reftable-leaks (ubuntu:rolling)
failed: t0410.35 promisor.quiet=false shows progress messages
linux-reftable-leaks (ubuntu:rolling)
failed: t0410.34 setup for promisor.quiet tests
linux-reftable-leaks (ubuntu:rolling)
failed: t0410.33 push should not fetch new commit objects
linux-reftable-leaks (ubuntu:rolling)
failed: t0410.32 lazy-fetch when accessing object not in the_repository
linux-reftable-leaks (ubuntu:rolling)
failed: t0410.31 exact rename does not need to fetch the blob lazily
linux-reftable-leaks (ubuntu:rolling)
failed: t0410.30 do not fetch when checking existence of tree we construct ourselves
linux-reftable-leaks (ubuntu:rolling)
failed: t0410.29 gc stops traversal when a missing but promised object is reached
linux-reftable-leaks (ubuntu:rolling)
failed: t0410.28 repack -d does not irreversibly delete promisor objects
linux-reftable-leaks (ubuntu:rolling)
failed: t0410.27 gc does not repack promisor objects if there are none
linux-reftable-leaks (ubuntu:rolling)
failed: t0410.26 gc repacks promisor objects separately from non-promisor objects
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/
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/

Artifacts

Produced during runtime
Name Size Digest
failed-tests-linux-leaks
827 KB
sha256:edf3dc16617ceee89d9b30f1bd00c7c7d61775e52f9ef864bf807bf22c01041c
failed-tests-linux-reftable-leaks
842 KB
sha256:ab30ff71f76be7f424e831df09c9ea6e59fd3aee206a1cd3de3079b8daeb00d8