From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [PATCH 0/4] Testsuite update
Date: Fri, 11 Aug 2023 14:41:44 +0100 [thread overview]
Message-ID: <f844a972-0b47-d480-e77f-c40107157e5b@dronecode.org.uk> (raw)
In-Reply-To: <ZNKHF2sbB6C55zoW@calimero.vinschen.de>
On 08/08/2023 19:19, Corinna Vinschen via Cygwin-apps wrote:
> On Aug 8 17:02, Jon Turney via Cygwin-apps wrote:
>> On 07/08/2023 09:55, Corinna Vinschen wrote:
>>> On Aug 4 13:47, Jon Turney wrote:
>>>> This gets us down to no permanent failures in the testsuite in CI.
>>
>> There is an intermittent failure in kill01, which I need to do something
>> about before turning on taking notice of the testsuite result in CI.
>>
>> Effectively, all this does is:
>>
>> pid = fork();
>> if (pid == 0) {
>> pause();
>> } else {
>> kill(pid, SIGKILL);
>> waitpid(pid, &status, 0);
>> }
>>
>> This is quite easy to demonstrate with 'winsup.api/ltp/kill01 -i 1000',
>> which repeats the test, succeeding until it hangs.
>>
>> Looking at the strace output, I would guess it's some race condition where a
>> child process isn't yet in a position to receive a signal immediately after
>> fork() returns in the parent (so the signal is dropped, and the parent
>> blocks indefinitely in waitpid waiting for the child to terminate)
>>
>> I'm not sure if that's fixable (or worth effort), so maybe just adding a
>> small delay in the test is the thing to do... :)
>
> It might be worth looking into it to make this more reliable, but the
> patch is fine for the time being, of course.
Thanks.
Sorry for sending this to the wrong list.
prev parent reply other threads:[~2023-08-11 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230804124723.9236-1-jon.turney@dronecode.org.uk>
[not found] ` <ZNCxkNhrpJWGRPbB@calimero.vinschen.de>
2023-08-08 16:02 ` Jon Turney
2023-08-08 18:19 ` Corinna Vinschen
2023-08-11 13:41 ` Jon Turney [this message]
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=f844a972-0b47-d480-e77f-c40107157e5b@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.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).