public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
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: Tue, 8 Aug 2023 17:02:42 +0100	[thread overview]
Message-ID: <e13edbb2-a1ce-009e-b40d-171a5a584791@dronecode.org.uk> (raw)
In-Reply-To: <ZNCxkNhrpJWGRPbB@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 997 bytes --]

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... :)

[-- Attachment #2: 0001-Cygwin-testsuite-Add-a-small-delay-in-kill01.patch --]
[-- Type: text/plain, Size: 848 bytes --]

From 3b7d7ae0f3c29de4d8e7ff0d4487bc6f7913dc86 Mon Sep 17 00:00:00 2001
From: Jon Turney <jon.turney@dronecode.org.uk>
Date: Tue, 8 Aug 2023 16:38:20 +0100
Subject: [PATCH] Cygwin: testsuite: Add a small delay in kill01

Avoid transient failures by adding a small delay after fork()-ing to
allow the child to get into a state where it can recieve signals.
---
 winsup/testsuite/winsup.api/ltp/kill01.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/winsup/testsuite/winsup.api/ltp/kill01.c b/winsup/testsuite/winsup.api/ltp/kill01.c
index 042899173..58053eeb8 100644
--- a/winsup/testsuite/winsup.api/ltp/kill01.c
+++ b/winsup/testsuite/winsup.api/ltp/kill01.c
@@ -102,6 +102,7 @@ main(int ac, char **av)
 			/*NOTREACHED*/
 			exit(exno);
 		} else {
+			Sleep(1);
 			TEST(kill(pid, TEST_SIG));
 			waitpid(pid, &status, 0);
 		}
-- 
2.39.0


       reply	other threads:[~2023-08-08 16:02 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 [this message]
2023-08-08 18:19     ` Corinna Vinschen
2023-08-11 13:41       ` Jon Turney

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=e13edbb2-a1ce-009e-b40d-171a5a584791@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).