From: Jeff King <peff@peff.net>
To: Jeffrey Walton <noloader@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Git port to Debian SH4 may have trouble
Date: Tue, 29 Nov 2022 14:02:31 -0500 [thread overview]
Message-ID: <Y4ZXRx4mf0UMk4H6@coredump.intra.peff.net> (raw)
In-Reply-To: <CAH8yC8niurChnXPrZSeBa7g1z5AF3PqYdf1X0Rm03rDanec6Gw@mail.gmail.com>
On Tue, Nov 29, 2022 at 12:01:01PM -0500, Jeffrey Walton wrote:
> This is a crummy bug report... I am testing on Debian Unstable within
> a SH4 Chroot. I'm seeing a hang during a git pull. Eventually I have
> to CTRL+C, which results in "fatal: fetch-pack: invalid index-pack
> output."
The message is probably a red herring. Once you terminate index-pack,
the fetch-pack process reading from it will see EOF before reading the
expected "pack ..." line, and generate that message.
So the hang is probably the only interesting part.
> (sh4) debian-chroot:~# git clone -vv https://github.com/weidai11/cryptopp
> Cloning into 'cryptopp'...
> POST git-upload-pack (175 bytes)
> want e9cbc4698a6b3ed067910862ad1355069f348d2b (HEAD)
> want e9cbc4698a6b3ed067910862ad1355069f348d2b (refs/heads/master)
> ...
> want 511806c0eba8ba5b5cedd4b4a814e96df92864a6 (refs/tags/CRYPTOPP_8_7_0)
> POST git-upload-pack (gzip 1602 to 825 bytes)
> remote: Enumerating objects: 28448, done.
> remote: Counting objects: 100% (68/68), done.
> remote: Compressing objects: 100% (50/50), done.
> remote: Total 28448 (delta 29), reused 49 (delta 18), pack-reused 28380
> Receiving objects: 100% (28448/28448), 27.01 MiB | 4.30 MiB/s, done.
> Resolving deltas: 0% (0/20757)
> ^Cfatal: fetch-pack: invalid index-pack output
If we're in the "resolving deltas" section, then that means we're
probably not hanging on receiving input from the remote side. At this
point we should have gotten all of the data and would be CPU-bound
reassembling deltas and computing their hashes.
Just a hunch, but does:
git config --global pack.threads 1
help? The delta resolution is multi-threaded, but nothing else in the
clone should be.
-Peff
next prev parent reply other threads:[~2022-11-29 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 17:01 Git port to Debian SH4 may have trouble Jeffrey Walton
2022-11-29 19:02 ` Jeff King [this message]
2022-11-29 21:49 ` Jeffrey Walton
2022-11-29 22:14 ` Jeff King
2022-11-29 22:33 ` Jeffrey Walton
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=Y4ZXRx4mf0UMk4H6@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=noloader@gmail.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.
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).