I'm trying to build Git 2.27.0 from sources on MACOS
I've got to get the build works solving missing autoconf app and gcov issues (clang does not need it)
now I'm struggling during the make profile
step
some tests fail on t0410-partial-clone.sh
not ok 15 - missing tree objects with --missing=allow-promisor and --exclude-promisor-objects
#
# rm -rf repo &&
# test_create_repo repo &&
# test_commit -C repo foo &&
# test_commit -C repo bar &&
# test_commit -C repo baz &&
#
# promise_and_delete $(git -C repo rev-parse bar^{tree}) &&
# promise_and_delete $(git -C repo rev-parse foo^{tree}) &&
#
# git -C repo config core.repositoryformatversion 1 &&
# git -C repo config extensions.partialclone "arbitrary string" &&
#
# git -C repo rev-list --missing=allow-promisor --objects HEAD >objs 2>rev_list_err &&
# test_must_be_empty rev_list_err &&
# # 3 commits, 3 blobs, and 1 tree
# test_line_count = 7 objs &&
#
# # Do the same for --exclude-promisor-objects, but with all trees gone.
# promise_and_delete $(git -C repo rev-parse baz^{tree}) &&
# git -C repo rev-list --exclude-promisor-objects --objects HEAD >objs 2>rev_list_err &&
# test_must_be_empty rev_list_err &&
# # 3 commits, no blobs or trees
# test_line_count = 3 objs
#
not ok 16 - missing non-root tree object and rev-list
#
# rm -rf repo &&
# test_create_repo repo &&
# mkdir repo/dir &&
# echo foo >repo/dir/foo &&
# git -C repo add dir/foo &&
# git -C repo commit -m "commit dir/foo" &&
#
# promise_and_delete $(git -C repo rev-parse HEAD:dir) &&
#
# git -C repo config core.repositoryformatversion 1 &&
# git -C repo config extensions.partialclone "arbitrary string" &&
#
# git -C repo rev-list --missing=allow-any --objects HEAD >objs 2>rev_list_err &&
# test_must_be_empty rev_list_err &&
# # 1 commit and 1 tree
# test_line_count = 2 objs
#
I'm a little surprised as presumed, since 2.27.0 is an official release, all the tests should pass without any issue.
I'm not interested to get latest version using home-brew so please leave it out of the answers
Any idea?
How to file a bug to the Git developers?
Aucun commentaire:
Enregistrer un commentaire