git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [BUG] More on t5562 hangs randomly in subtests 6,8 and 13 in 2.21.0-rc0

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 18, 2019, 20:14 UTC
Message-ID
<nycvar.QRO.7.76.6.1902182105520.45@tvgsbejvaqbjf.bet>
In-Reply-To
<20190213174055.GD3064@jessie.local>
Hi Max,
On Wed, 13 Feb 2019, Max Kirillov wrote:
Show 12 quoted lines
> 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

Previous: Randall S. Becker
Message 4 of 4 in “Re: [BUG] More on t5562 hangs randomly in subtests 6,8 and 13 in 2.21.0-rc0”
  1. randall.s.becker@rogers.comFeb 13, 2019
  2. Max KirillovFeb 13, 2019
  3. Randall S. BeckerFeb 13, 2019
  4. Johannes SchindelinFeb 18, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.