From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org, Jonathan Tan <jonathantanmy@google.com>
Subject: What's so special about almalinux-8?
Date: Mon, 04 Nov 2024 21:54:16 -0800 [thread overview]
Message-ID: <xmqqbjyuted3.fsf@gitster.g> (raw)
Everybody else seems to pass tests, but not this one
https://github.com/git/git/actions/runs/11677884048/job/32516504151#step:6:1995
I am not (yet) so familiar with the topics in flight at this point,
but there are a few topics that deal with packing, lazy fetching,
and commit-graph and object database being out of sync, which were
handled by a few topics by Jonathan, so I am CC'ing this if it rings
bell for him.
failure: t5616.22 use fsck before and after manually fetching a missing subtree
# push new commit so server has a subtree
mkdir src/dir &&
echo "in dir" >src/dir/file.txt &&
git -C src add dir/file.txt &&
git -C src commit -m "file in dir" &&
git -C src push -u srv main &&
SUBTREE=$(git -C src rev-parse HEAD:dir) &&
rm -rf dst &&
git clone --no-checkout --filter=tree:0 "file://$(pwd)/srv.bare" dst &&
git -C dst fsck &&
# Make sure we only have commits, and all trees and blobs are missing.
git -C dst rev-list --missing=allow-any --objects main \
>fetched_objects &&
awk -f print_1.awk fetched_objects |
xargs -n1 git -C dst cat-file -t >fetched_types &&
sort -u fetched_types >unique_types.observed &&
echo commit >unique_types.expected &&
test_cmp unique_types.expected unique_types.observed &&
# Auto-fetch a tree with cat-file.
git -C dst cat-file -p $SUBTREE >tree_contents &&
grep file.txt tree_contents &&
# fsck still works after an auto-fetch of a tree.
git -C dst fsck &&
# Auto-fetch all remaining trees and blobs with --missing=error
git -C dst rev-list --missing=error --objects main >fetched_objects &&
test_line_count = 88 fetched_objects &&
awk -f print_1.awk fetched_objects |
xargs -n1 git -C dst cat-file -t >fetched_types &&
sort -u fetched_types >unique_types.observed &&
test_write_lines blob commit tree >unique_types.expected &&
test_cmp unique_types.expected unique_types.observed
++ mkdir src/dir
++ echo 'in dir'
++ git -C src add dir/file.txt
++ git -C src commit -m 'file in dir'
[main 957c60b] file in dir
Author: A U Thor <author@example.com>
1 file changed, 1 insertion(+)
create mode 100644 dir/file.txt
++ git -C src push -u srv main
To file:///__w/git/git/t/trash directory.t5616-partial-clone/srv.bare
129c8a2..957c60b main -> main
branch 'main' set up to track 'srv/main'.
+++ git -C src rev-parse HEAD:dir
++ SUBTREE=bc1967ebf96a4e914801c7ef8328140456a10f41
++ rm -rf dst
+++ pwd
++ git clone --no-checkout --filter=tree:0 'file:///__w/git/git/t/trash directory.t5616-partial-clone/srv.bare' dst
Cloning into 'dst'...
++ git -C dst fsck
++ git -C dst rev-list --missing=allow-any --objects main
++ awk -f print_1.awk fetched_objects
++ xargs -n1 git -C dst cat-file -t
++ sort -u fetched_types
++ echo commit
++ test_cmp unique_types.expected unique_types.observed
++ test 2 -ne 2
++ eval 'diff -u' '"$@"'
+++ diff -u unique_types.expected unique_types.observed
++ git -C dst cat-file -p bc1967ebf96a4e914801c7ef8328140456a10f41
++ grep file.txt tree_contents
100644 blob d2cebd4f0a9e97a48a6139d09cafdb513ad8fee3 file.txt
++ git -C dst fsck
dangling tree bc1967ebf96a4e914801c7ef8328140456a10f41
++ git -C dst rev-list --missing=error --objects main
fatal: You are attempting to fetch 957c60b67968d2ab4144e7e2fbba99d6ad864e4e, which is in the commit graph file but not in the object database.
This is probably due to repo corruption.
If you are attempting to repair this repo corruption by refetching the missing object, use 'git fetch --refetch' with the missing object.
fatal: could not fetch 3246c304205324149983025431c5211438f41931 from promisor remote
error: last command exited with $?=128
not ok 22 - use fsck before and after manually fetching a missing subtree
next reply other threads:[~2024-11-05 5:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 5:54 Junio C Hamano [this message]
2024-11-05 18:54 ` What's so special about almalinux-8? Jonathan Tan
2024-11-06 0:31 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqbjyuted3.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jonathantanmy@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.