# Re: [BUG] More on t5562 hangs randomly in subtests 6,8 and 13 in 2.21.0-rc0 4 messages from 2019-02-13 to 2019-02-18. Participants: randall.s.becker@rogers.com, Max Kirillov, Randall S. Becker, Johannes Schindelin. Thread: https://gitlist.dev/t/50493 ## randall.s.becker@rogers.com, 2019-02-13 15:16 Subject: Re: [BUG] More on t5562 hangs randomly in subtests 6,8 and 13 in 2.21.0-rc0 Message-ID: <000501d4c3af$1748b100$45da1300$@rogers.com> URL: https://gitlist.dev/e/000501d4c3af%241748b100%2445da1300%24%40rogers.com ``` 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 ``` ## Max Kirillov, 2019-02-13 17:40 Subject: Re: [BUG] More on t5562 hangs randomly in subtests 6,8 and 13 in 2.21.0-rc0 Message-ID: <20190213174055.GD3064@jessie.local> URL: https://gitlist.dev/e/20190213174055.GD3064%40jessie.local In-Reply-To: <000501d4c3af$1748b100$45da1300$@rogers.com> ``` 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? ``` ## Randall S. Becker, 2019-02-13 18:20 Subject: RE: [BUG] More on t5562 hangs randomly in subtests 6,8 and 13 in 2.21.0-rc0 Message-ID: <004801d4c3c8$df9d23c0$9ed76b40$@nexbridge.com> URL: https://gitlist.dev/e/004801d4c3c8%24df9d23c0%249ed76b40%24%40nexbridge.com 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. ``` ## Johannes Schindelin, 2019-02-18 20:14 Subject: Re: [BUG] More on t5562 hangs randomly in subtests 6,8 and 13 in 2.21.0-rc0 Message-ID: URL: https://gitlist.dev/e/nycvar.QRO.7.76.6.1902182105520.45%40tvgsbejvaqbjf.bet In-Reply-To: <20190213174055.GD3064@jessie.local> ``` Hi Max, On Wed, 13 Feb 2019, 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? That is an interesting question. From what I can see, the `gzipped_request` flag guards a call to `inflate_request()`, which does not explicitly close stdin, is all I could see. But it does not spawn a sub-process from what I can see, other than the regular backend ("upload-pack" or "receive-pack"). Ciao, Dscho ```