From: Junio C Hamano <gitster@pobox.com>
To: tsuna <tsunanet@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Deadlock between git-remote-http and git fetch-pack
Date: Fri, 27 Jan 2017 15:34:21 -0800 [thread overview]
Message-ID: <xmqqefzoxeki.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAFKYj4cMSK5nQ1nS66c4Opz8y7x+xQH+OdW8PTi7LmCiGBP1ZA@mail.gmail.com> (tsuna's message of "Fri, 27 Jan 2017 14:31:15 -0800")
tsuna <tsunanet@gmail.com> writes:
> While investigating a hung job in our CI system today, I think I found
> a deadlock in git-remote-http
> ...
> Here PID 27319 (git fetch-pack) is stuck reading on stdin, while its
> parent, PID 27317 (git-remote-http) is stuck reading on its child’s
> stdout. Nothing has moved for like 2h, it’s deadlocked.
Hmph, would this be related to 296b847c0d ("remote-curl: don't hang
when a server dies before any output", 2016-11-18) I wonder...
prev parent reply other threads:[~2017-01-28 0:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 22:31 Deadlock between git-remote-http and git fetch-pack tsuna
2017-01-27 23:19 ` Jonathan Tan
2017-01-27 23:34 ` Junio C Hamano [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqefzoxeki.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=tsunanet@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox