From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Max Kirillov'" <max@max630.net>
Cc: "'Git List'" <git@vger.kernel.org>
Subject: RE: [BUG] More on t5562 hangs randomly in subtests 6,8 and 13 in 2.21.0-rc0
Date: Wed, 13 Feb 2019 13:20:55 -0500 [thread overview]
Message-ID: <004801d4c3c8$df9d23c0$9ed76b40$@nexbridge.com> (raw)
In-Reply-To: <20190213174055.GD3064@jessie.local>
On February 13, 2019 12:41, Max Kirillov wrote:
> On Wed, Feb 13, 2019 at 10:16:26AM -0500, randall.s.becker@rogers.com
> wrote:
> > On 2019-02-13, Max Kirillov, wrote:
> > 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.
>
> You mentioned cases 6,8,13. These are all related to gipped request body.
> Could it be the git-http-backend does not clean a sub-process which
> pervforms the decompression?
I guess that is possible. I don't know the guts of this part of the code.
next prev parent reply other threads:[~2019-02-13 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 15:16 [BUG] More on t5562 hangs randomly in subtests 6,8 and 13 in 2.21.0-rc0 randall.s.becker
2019-02-13 17:40 ` Max Kirillov
2019-02-13 18:20 ` Randall S. Becker [this message]
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='004801d4c3c8$df9d23c0$9ed76b40$@nexbridge.com' \
--to=rsbecker@nexbridge.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).