On Tue, Mar 22, 2016 at 02:38:34PM -0700, Stefan Beller wrote: > On Tue, Mar 22, 2016 at 11:22 AM, Stefan Beller <sbel...@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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
