From: Thomas Rast <trast@student.ethz.ch>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: <git@vger.kernel.org>
Subject: Re: t1450-fsck (sometimes/often) failes on Mac OS X
Date: Mon, 16 Jul 2012 09:57:50 +0200 [thread overview]
Message-ID: <87y5mkm935.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <5001644F.10901@web.de> ("Torsten Bögershausen"'s message of "Sat, 14 Jul 2012 14:21:35 +0200")
Torsten Bögershausen <tboegi@web.de> writes:
> Now it appeared on next as well, so it's time to look a little bit deeper.
>
> This test case of t1450 fails:
> test_expect_success 'tag pointing to something else than its type' '
>
> To debug more, I added an exit 0 here to inspect the file named out:
> diff --git a/t/t1450-fsck.sh b/t/t1450-fsck.sh
> index 5b79c51..f1f45c9 100755
> --- a/t/t1450-fsck.sh
> +++ b/t/t1450-fsck.sh
> @@ -179,6 +179,7 @@ test_expect_success 'tag pointing to something else than its type' '
> test_when_finished "git update-ref -d refs/tags/wrong" &&
> test_must_fail git fsck --tags 2>out &&
> cat out &&
> + exit 0
> grep "error in tag.*broken links" out
> '
>
> Linux:
> error: Object 63499e4ea8e096b831515ceb1d5a7593e4d87ae5 is a blob, not a commit
> error in tag 66f6581d549f70e05ca586bc2df5c15a95662c36: broken links
> error in tag 66f6581d549f70e05ca586bc2df5c15a95662c36: could not load tagged object
>
> Mac OS X:
> error: Object 63499e4ea8e096b831515ceb1d5a7593e4d87ae5 is a commit, not a blob
> error: 63499e4ea8e096b831515ceb1d5a7593e4d87ae5: object corrupt or missing
What OS X are you running? I started a loop
while : ; do ./t1450-fsck.sh || break; done
and it hasn't failed yet. It is
$ uname -a
Darwin mackeller.inf.ethz.ch 11.4.0 Darwin Kernel Version 11.4.0: Mon Apr 9 19:32:15 PDT 2012; root:xnu-1699.26.8~1/RELEASE_X86_64 x86_64
> I reverted the last change in fsck.c (Use the streaming interface), but that doesn't help
>
> Looking into the trash directory and looking at the files, we can see that the .git/index is different
> between Linux and Mac OS X.
>
> Is there a good way to debug the index file?
You can run 'git ls-files --debug' which should give you all the data in
the index, and then perhaps run diff over that to determine the
differences...
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-07-16 7:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-14 12:21 t1450-fsck (sometimes/often) failes on Mac OS X Torsten Bögershausen
2012-07-15 9:08 ` Jeff King
2012-07-15 13:03 ` Torsten Bögershausen
2012-09-19 16:04 ` Torsten Bögershausen
2012-09-19 18:30 ` Junio C Hamano
2012-09-19 20:23 ` Torsten Bögershausen
2012-10-02 16:06 ` Torsten Bögershausen
2012-10-02 21:01 ` Junio C Hamano
2012-10-02 22:21 ` Junio C Hamano
2012-10-03 19:37 ` Torsten Bögershausen
2012-07-16 7:57 ` Thomas Rast [this message]
2012-07-16 16:06 ` Torsten Bögershausen
2012-07-28 15:43 ` Heiko Voigt
2012-07-28 16:00 ` Thomas Rast
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y5mkm935.fsf@thomas.inf.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=tboegi@web.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).