From: Jeff King <peff@peff.net>
To: Brian Gernhardt <benji@silverinsanity.com>
Cc: "git@vger.kernel.org List" <git@vger.kernel.org>
Subject: Re: Intermittent Failures in t1450-fsck (Bisected)
Date: Thu, 5 May 2011 17:03:17 -0400 [thread overview]
Message-ID: <20110505210317.GE1770@sigill.intra.peff.net> (raw)
In-Reply-To: <60194977-A4A9-4E18-9878-C1CDE77B75C2@silverinsanity.com>
On Thu, May 05, 2011 at 04:04:33PM -0400, Brian Gernhardt wrote:
> The original e-mail was from next at that point. The output from the
> rebased version and current next (76e37e2) is identical.
Thanks. The weird thing is that running t1450 on 76e37e2 gives me this
output:
broken link from tag 66f6581d549f70e05ca586bc2df5c15a95662c36
broken link from unknown unknown
dangling blob 63499e4ea8e096b831515ceb1d5a7593e4d87ae5
error: Object 63499e4ea8e096b831515ceb1d5a7593e4d87ae5 is a blob, not a commit
error in tag 66f6581d549f70e05ca586bc2df5c15a95662c36: broken links
error in tag 66f6581d549f70e05ca586bc2df5c15a95662c36: could not load tagged object
error in tag 66f6581d549f70e05ca586bc2df5c15a95662c36: broken links
whereas from your original email, you had:
> >>> tagged commit 63499e4ea8e096b831515ceb1d5a7593e4d87ae5 (wrong) in 66f6581d549f70e05ca586bc2df5c15a95662c36
> >>> missing commit 63499e4ea8e096b831515ceb1d5a7593e4d87ae5
> >>> error: Object 63499e4ea8e096b831515ceb1d5a7593e4d87ae5 is a commit, not a blob
> >>> error: 63499e4ea8e096b831515ceb1d5a7593e4d87ae5: object corrupt or missing
which is weird. We do call "remove_object $sha", but only inside
test_when_finished. I wonder if there is some bug with
test_when_finished on your platform. Have you tried instrumenting the
remove_object function to print a message when it is run? That might
give us a clue if it is accidentally being run early.
> This is on my OS X laptop and last I knew valgrind was very buggy on
> OS X, so I've never tried it. I'll install it now and see if I can
> get anything useful out of it.
I've tried but been unable to reproduce on Linux, so it seems like
something OS X specific.
-Peff
next prev parent reply other threads:[~2011-05-05 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 17:11 Intermittent Failures in t1450-fsck Brian Gernhardt
2011-05-05 6:46 ` Intermittent Failures in t1450-fsck (Bisected) Brian Gernhardt
2011-05-05 9:32 ` Jeff King
2011-05-05 20:04 ` Brian Gernhardt
2011-05-05 21:03 ` Jeff King [this message]
2011-05-05 21:58 ` Brian Gernhardt
2011-05-07 20:25 ` Brian Gernhardt
2011-05-11 11:43 ` Jeff King
2011-05-05 21:07 ` Brian Gernhardt
2011-05-05 21:17 ` 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=20110505210317.GE1770@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=benji@silverinsanity.com \
--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).