git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Evan Miller <emmiller@gmail.com>
To: git@vger.kernel.org
Subject: Re: Exit code 255 after large clone (32-bit PowerPC)
Date: Mon, 26 Jul 2021 22:08:33 -0400	[thread overview]
Message-ID: <89D261C9-A97C-4FD2-9FB5-ACCDA2E70CE0@gmail.com> (raw)
In-Reply-To: <874kcgsh94.fsf@evledraar.gmail.com>


> On Jul 26, 2021, at 20:51, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
> 
> Evan: Can you run this with some of GIT_TRACE=1 /
> GIT_TRACE_EVENT=/dev/stderr GIT_TRACE_PACKET=1 and see if some of those
> show what's happening in/around that 255 exit?

Running it again – the "Connection closed" message appears while the Deltas are being computed. Until that message appears, the ssh process is still alive.

There are no trace messages immediately surrounding the closed connection. The 255 exit does not occur until after the deltas are computed and the updates are resolved. (Which makes the error confusing from a user perspective.)

I would think that the SSH connection could/should be closed immediately after all the objects have been received. I am still compiling a more recent SSH, and will report back tomorrow if that changes anything. As of this writing:

$ ssh -v
OpenSSH_5.1p1, OpenSSL 0.9.7l 28 Sep 2006

Evan

      parent reply	other threads:[~2021-07-27  2:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-26 17:54 Exit code 255 after large clone (32-bit PowerPC) Evan Miller
2021-07-26 22:09 ` brian m. carlson
2021-07-26 22:50   ` Evan Miller
2021-07-27  0:51   ` Ævar Arnfjörð Bjarmason
2021-07-27  1:37     ` brian m. carlson
2021-07-27  2:20       ` Junio C Hamano
2021-07-27  3:05         ` Evan Miller
2021-07-27 12:44           ` Jeff King
2021-07-27  2:08     ` Evan Miller [this message]

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=89D261C9-A97C-4FD2-9FB5-ACCDA2E70CE0@gmail.com \
    --to=emmiller@gmail.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. 
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).