From: Max Kirillov <max@max630.net>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: 'Johannes Schindelin via GitGitGadget' <gitgitgadget@gmail.com>,
git@vger.kernel.org, 'Junio C Hamano' <gitster@pobox.com>,
'Max Kirillov' <max@max630.net>
Subject: Re: [PATCH 0/1] Fix hang in t5562, introduced in v2.21.0-rc1
Date: Fri, 15 Feb 2019 00:33:34 +0200 [thread overview]
Message-ID: <20190214223334.GE3064@jessie.local> (raw)
In-Reply-To: <005401d4c4b3$147aa8c0$3d6ffa40$@nexbridge.com>
On Thu, Feb 14, 2019 at 05:17:26PM -0500, Randall S. Becker wrote:
> Unfortunately, subtest 13 still hangs on NonStop, even
> with this patch, so our Pipeline still hangs. I'm glad
> it's better on Azure, but I don't think this actually
> addresses the root cause of the hang. This is now the
> fourth attempt at fixing this. Is it possible this is not
> the test that is failing, but actually the
> git-http-backend? The code is not in a loop, if that
> helps. It is not consuming any significant cycles. I don't
> know that part of the code at all, sadly. The code is
> here:
>
> * in the operating system from here up *
> cleanup_children + 0x5D0 (UCr)
... so does the process which the stack was taken from has
any children processes still?
I could imagine if a child somehow manages to end up in
uninterruptible sleep, then probably it would never complete
this way, wouldn't it?
next prev parent reply other threads:[~2019-02-14 22:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 21:33 [PATCH 0/1] Fix hang in t5562, introduced in v2.21.0-rc1 Johannes Schindelin via GitGitGadget
2019-02-14 21:33 ` [PATCH 1/1] tests: teach the test-tool to generate NUL bytes and use it Johannes Schindelin via GitGitGadget
2019-02-14 22:13 ` Junio C Hamano
2019-02-15 14:59 ` Johannes Schindelin
2019-02-15 17:41 ` Junio C Hamano
2019-02-18 15:55 ` Johannes Schindelin
2019-02-14 22:17 ` [PATCH 0/1] Fix hang in t5562, introduced in v2.21.0-rc1 Randall S. Becker
2019-02-14 22:33 ` Max Kirillov [this message]
2019-02-14 22:59 ` Randall S. Becker
2019-02-14 23:04 ` Randall S. Becker
2019-02-14 22:38 ` Junio C Hamano
2019-02-14 23:01 ` Randall S. Becker
2019-02-18 20:41 ` Johannes Schindelin
2019-02-18 20:46 ` Randall S. Becker
2019-02-18 20:57 ` Max Kirillov
2019-02-19 14:09 ` Johannes Schindelin
2019-02-18 20:57 ` Randall S. Becker
2019-02-18 21:49 ` Randall S. Becker
2019-02-18 21:06 ` Ævar Arnfjörð Bjarmason
2019-02-18 21:17 ` Max Kirillov
2019-02-19 14:13 ` Johannes Schindelin
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=20190214223334.GE3064@jessie.local \
--to=max@max630.net \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=rsbecker@nexbridge.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).