From: <randall.s.becker@rogers.com>
To: "'Git List'" <git@vger.kernel.org>
Cc: <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 10:16:26 -0500 [thread overview]
Message-ID: <000501d4c3af$1748b100$45da1300$@rogers.com> (raw)
On 2019-02-13, Max Kirillov, wrote:
>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.
>
>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?
I don't think the lack of curl is an issue (one thing mentioned in the
thread), as curl works fine. We are on 7.57.0.
As far as the unintended reuse of the output file, and issues with pipes,
yes, the NonStop is very sensitive to complex use of pipes and much of the
compatibility issues we have had relate to those (usually Linux-specific
pipe assumptions). That is where I have been looking when trying to debug
this situation (not yet found anything). This could very well be directly
related.
Regards,
Randall
next reply other threads:[~2019-02-13 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 15:16 randall.s.becker [this message]
2019-02-13 17:40 ` [BUG] More on t5562 hangs randomly in subtests 6,8 and 13 in 2.21.0-rc0 Max Kirillov
2019-02-13 18:20 ` Randall S. Becker
2019-02-18 20:14 ` Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2019-02-11 16:59 Randall S. Becker
2019-02-13 4:30 ` Max Kirillov
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='000501d4c3af$1748b100$45da1300$@rogers.com' \
--to=randall.s.becker@rogers.com \
--cc=git@vger.kernel.org \
--cc=max@max630.net \
/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).