From: "A. Wilcox" <awilfox@adelielinux.org>
To: git@vger.kernel.org
Subject: Git 2.14.1: t6500: error during test on musl libc
Date: Thu, 14 Sep 2017 21:43:12 -0500 [thread overview]
Message-ID: <59BB3E40.7020804@adelielinux.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi there,
While bumping Git's version for our Linux distribution to 2.14.1, I've
run in to a new test failure in t6500-gc.sh. This is the output of
the failing test with debug=t verbose=t:
expecting success:
# make sure we run a background auto-gc
test_commit make-pack &&
git repack &&
test_config gc.autopacklimit 1 &&
test_config gc.autodetach true &&
# create a ref whose loose presence we can use to detect a
pack-refs run
git update-ref refs/heads/should-be-loose HEAD &&
test_path_is_file .git/refs/heads/should-be-loose &&
# now fake a concurrent gc that holds the lock; we can use our
# shell pid so that it looks valid.
hostname=$(hostname || echo unknown) &&
printf "$$ %s" "$hostname" >.git/gc.pid &&
# our gc should exit zero without doing anything
run_and_wait_for_auto_gc &&
test_path_is_file .git/refs/heads/should-be-loose
[master 28ecdda] make-pack
Author: A U Thor <author@example.com>
1 file changed, 1 insertion(+)
create mode 100644 make-pack.t
Counting objects: 3, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), done.
Total 3 (delta 0), reused 0 (delta 0)
Auto packing the repository in background for optimum performance.
See "git help gc" for manual housekeeping.
File .git/refs/heads/should-be-loose doesn't exist.
not ok 8 - background auto gc respects lock for all operations
#
# # make sure we run a background auto-gc
# test_commit make-pack &&
# git repack &&
# test_config gc.autopacklimit 1 &&
# test_config gc.autodetach true &&
#
# # create a ref whose loose presence we can use to
detect a pack-refs run
# git update-ref refs/heads/should-be-loose HEAD &&
# test_path_is_file .git/refs/heads/should-be-loose &&
#
# # now fake a concurrent gc that holds the lock; we can
use our
# # shell pid so that it looks valid.
# hostname=$(hostname || echo unknown) &&
# printf "$$ %s" "$hostname" >.git/gc.pid &&
#
# # our gc should exit zero without doing anything
# run_and_wait_for_auto_gc &&
# test_path_is_file .git/refs/heads/should-be-loose
#
# failed 1 among 8 test(s)
1..8
I admit I am mostly blind with the Git gc system. Should I use strace
on the git-gc process at the end? How would I accomplish that? Is
there a better way of debugging this error further?
Core system stats:
Intel x86_64 E3-1280 v3 @ 3.60 GHz
musl libc 1.1.16+20
git 2.14.1, vanilla except for a patch to an earlier test due to
musl's inability to cope with EUC-JP
bash 4.3.48(1)-release
Thank you very much.
All the best,
- --arw
- --
A. Wilcox (awilfox)
Project Lead, Adélie Linux
http://adelielinux.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJZuz4yAAoJEMspy1GSK50UORwP/0Jxfp3xzexh27tSJlXYWS/g
g9QK8Xmid+3A0R696Vb2GguKg2roCcTmM2anR7iD1B2f2W31sgf+8M5mnJRHyJ1p
geEeqwrTdpCk6jQ/1Pj03L0NOftb1ftR6hcoVujBFAOph4jRlRdZDPA87fe6snrh
q99C3LoDXQcyK6WWJwzX+t2wOplKgpGJP8wTAaZ0AHoUwVS5CLPl8tP2XaY4kLfD
ZPPcvtp9wisVzzZ2ssE/CLGd38EbenNNZ6OJCBFJIHmlwey4G2isZ9kk6fVIHXi2
unBJ8yVqI7hQKmQFSVQMMSFSd9azhHnDjTBO5mzWeRK9HNVMda3LZsXTtVeswnRs
lN/ASMdt5KdfpNy/plFB7yDWLlQSQY7j1mxBMR8lL3AdVVQUbJppDM795tt+rn6a
NCE2ESZMWd/QEULmT92AbkNJTj5ibBEoubnVTka05KMjaBLwIauhpqU5XxLFq2UH
y3JYQU9hm0E7dQE0CLXxIm5/574T6bBUgp1cXH3CjxkeUYKR1USVKtDfBV6t/Qmt
xlDZKPEfjKbTvL3KUF33G+eAp55wTwrJTaWlOp8A/JqooXavYghcsuFhYtCPJ8qo
fFUa8kBZP70E/O7JkycUu8wi7p42+j1a8gR6/AnPG2u2wyoiosLCxHX+nll4gKmN
b6BuiRn0Z9ie5xw4xcMR
=Vf8Z
-----END PGP SIGNATURE-----
next reply other threads:[~2017-09-15 2:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 2:43 A. Wilcox [this message]
2017-09-15 6:37 ` Git 2.14.1: t6500: error during test on musl libc Kevin Daudt
2017-09-15 6:43 ` Kevin Daudt
2017-09-15 11:30 ` Jeff King
2017-09-16 4:58 ` A. Wilcox
2017-09-16 16:13 ` [musl] " Rich Felker
2017-09-17 0:36 ` Junio C Hamano
2017-09-17 1:17 ` [musl] " Szabolcs Nagy
2017-09-17 1:58 ` A. Wilcox
2017-09-17 3:16 ` Junio C Hamano
2017-09-17 3:38 ` A. Wilcox
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=59BB3E40.7020804@adelielinux.org \
--to=awilfox@adelielinux.org \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).