From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: Jeremy Drake <cygwin@jdrake.com>
Subject: Re: pipe hang issue when running as SYSTEM
Date: Fri, 25 Mar 2022 20:11:04 +0900 [thread overview]
Message-ID: <20220325201104.d4524e351143acbee689161f@nifty.ne.jp> (raw)
In-Reply-To: <alpine.BSO.2.21.2203250009170.56460@resin.csoft.net>
On Fri, 25 Mar 2022 00:09:59 -0700 (PDT)
Jeremy Drake wrote:
> On Fri, 25 Mar 2022, Takashi Yano wrote:
>
> > I can confirm the sample script hangs indeed if the script is
> > running as SYSTEM account. However, in my test, the patch solves
> > the issue.
> >
> > It would be very helpfull if a simple github repository with
> > github actions, which can reproduce the issue, is provided.
>
> After much fighting with docker on windows,
> https://github.com/jeremyd2019/msys2-pipe-hang-test/runs/5688176578?check_suite_focus=true
Thanks much! I could reproduce the issue even with the patch.
I also noticed what is the cause.
The problem is that the command:
docker run msys2-base c:\msys64\usr\bin\bash -lc "/c/test.sh"
does not allocate tty. Therefore, kill_pgrp(__SIGNONCYGCHLD)
is not called.
If you use:
docker run -t msys2-base c:\msys64\usr\bin\bash -lc "/c/test.sh"
the problem does not occur.
I will submit v3 patch shortly.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2022-03-25 11:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 18:45 Jeremy Drake
2022-03-22 10:18 ` Takashi Yano
2022-03-22 13:17 ` Takashi Yano
2022-03-25 3:42 ` Jeremy Drake
2022-03-25 5:42 ` Takashi Yano
2022-03-25 7:09 ` Jeremy Drake
2022-03-25 11:11 ` Takashi Yano [this message]
2022-03-25 17:01 ` Jeremy Drake
2022-03-29 9:11 ` Takashi Yano
2022-03-25 7:48 ` Roumen Petrov
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=20220325201104.d4524e351143acbee689161f@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@cygwin.com \
--cc=cygwin@jdrake.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 read-only IMAP folder(s) and NNTP newsgroup(s).