From: Max Kirillov <max@max630.net>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: git@vger.kernel.org, max@max630.net
Subject: Re: [BUG] More on t5562 hangs randomly in subtests 6,8 and 13 in 2.21.0-rc0
Date: Wed, 13 Feb 2019 06:30:28 +0200 [thread overview]
Message-ID: <20190213043028.GC3064@jessie.local> (raw)
In-Reply-To: <001901d4c22b$194bfe60$4be3fb20$@nexbridge.com>
On Mon, Feb 11, 2019 at 11:59:00AM -0500, Randall S. Becker wrote:
> Hi All,
>
> I have localized the hang in t5562 (previous thread) to the
> invoke-with-content-length.pl script.
Hi.
I have not noticed the previous thread.
I have yet to look at it more closely, but there have been
one case of misbehavior due to unintended reuse of output file (see
https://public-inbox.org/git/20181119101535.16538-1-carenas@gmail.com/ )
Could your case be somehow related to it?
next prev parent reply other threads:[~2019-02-13 4:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 16:59 [BUG] More on t5562 hangs randomly in subtests 6,8 and 13 in 2.21.0-rc0 Randall S. Becker
2019-02-13 4:30 ` Max Kirillov [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-13 15:16 randall.s.becker
2019-02-13 17:40 ` Max Kirillov
2019-02-13 18:20 ` Randall S. Becker
2019-02-18 20:14 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190213043028.GC3064@jessie.local \
--to=max@max630.net \
--cc=git@vger.kernel.org \
--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.
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).