From: Jeff King <peff@peff.net>
To: Stefan Beller <sbeller@google.com>
Cc: Marcus T <maddimax@googlemail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git fails updating submodule only if --quiet is specified
Date: Tue, 22 Mar 2016 18:25:01 -0400 [thread overview]
Message-ID: <20160322222501.GA29577@sigill.intra.peff.net> (raw)
In-Reply-To: <CAGZ79kb0izRAZoQaDxTjKNz0VFEBqbkCSmro2pHm_kmLpJk0mw@mail.gmail.com>
On Tue, Mar 22, 2016 at 02:38:34PM -0700, Stefan Beller wrote:
> On Tue, Mar 22, 2016 at 11:22 AM, Stefan Beller <sbeller@google.com> wrote:
> > However lookingat your logs, I would suspect it is an error in git
> > clone instead, as that is the
> > last command which has the --quiet flag passed through the stack.
>
> git clone --no-checkout --quiet --separate-git-dir tmp_gitdir
> git://git.busybox.net/buildroot tmp_workdir
> fails as a standalone program as well, so let's debug that.
I think you can simplify this quite a bit to just:
git clone --quiet git://git.busybox.net/buildroot
That breaks, but works without --quiet. Presumably the problem is on the
server side, as we see the remote end hang up (and using different
versions of git on the client does not seem to help).
It seems to fail consistently for me around 2.4s, which makes me think
we're hitting some kind of timeout. I'd suspect a bug in the keep-alive
code in upload-pack, but that shouldn't have kicked in by then.
I guess the next step is to try to reproduce with a local client/server,
and then bisect the server version.
-Peff
next prev parent reply other threads:[~2016-03-22 22:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 15:02 git fails updating submodule only if --quiet is specified Marcus T
2016-03-22 15:51 ` Marcus T
2016-03-22 18:22 ` Stefan Beller
2016-03-22 21:38 ` Stefan Beller
2016-03-22 21:43 ` Stefan Beller
[not found] ` <CALgWkErHQ=coXRpzxY0jQoAN1pM-X9-UbPQUbNE56xhnb2VHfg@mail.gmail.com>
2016-03-22 22:02 ` Stefan Beller
2016-03-22 22:25 ` Jeff King [this message]
2016-03-22 22:35 ` 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=20160322222501.GA29577@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=maddimax@googlemail.com \
--cc=sbeller@google.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.
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).