From: Bruno Haible <bruno@clisp.org>
To: Eric Blake <eblake@redhat.com>
Cc: bug-gnulib@gnu.org
Subject: Re: execute tests: Avoid test failure on Android
Date: Tue, 17 Jan 2023 22:15:54 +0100 [thread overview]
Message-ID: <1982183.1Y0LTTvt8K@nimes> (raw)
In-Reply-To: <20230117194201.mt6hsgxxwyjoyusv@redhat.com>
Eric Blake wrote:
> > Apparently the SIGPIPE handler gets set to SIG_IGN, either by 'make' or
> > by the test-driver.
>
> Known regression in make 4.4:
> https://savannah.gnu.org/bugs/index.php?63307
Thanks. Indeed, I can reproduce the test failure also on a glibc system,
with make 4.4 in $PATH. Thus I'm generalizing the workaround:
2023-01-17 Bruno Haible <bruno@clisp.org>
execute tests: Avoid test failure with GNU make 4.4.
Reported by Eric Blake in
<https://lists.gnu.org/archive/html/bug-gnulib/2023-01/msg00157.html>.
* tests/test-execute-main.c (main): Reset the SIGPIPE handler to
default on all platforms.
diff --git a/tests/test-execute-main.c b/tests/test-execute-main.c
index fbaa9c9d2e..2088408756 100644
--- a/tests/test-execute-main.c
+++ b/tests/test-execute-main.c
@@ -58,17 +58,16 @@ main (int argc, char *argv[])
const char *progname = "test-execute-child";
int test = atoi (argv[2]);
-#if defined __ANDROID__
- /* On Android 11, when this test is executed through 'make' (GNU make 4.4) and
+ /* When this test is executed through 'make' (GNU make 4.4) and
build-aux/test-driver, i.e. through
make check TESTS=test-execute.sh
or
rm -f test-execute.sh.log; make test-execute.sh.log
- the signal handler for SIGPIPE is set to SIG_IGN. This causes the tests
- 3 and 4 to fail. Work around it by resetting the signal handler for
- SIGPIPE to the default. */
+ the signal handler for SIGPIPE is set to SIG_IGN. This is a bug in
+ GNU make 4.4: <https://savannah.gnu.org/bugs/index.php?63307>.
+ It causes the tests 3 and 4 to fail. Work around it by resetting
+ the signal handler for SIGPIPE to the default. */
signal (SIGPIPE, SIG_DFL);
-#endif
switch (test)
{
prev parent reply other threads:[~2023-01-17 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 14:21 execute tests: Avoid test failure on Android Bruno Haible
2023-01-17 19:42 ` Eric Blake
2023-01-17 21:15 ` Bruno Haible [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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1982183.1Y0LTTvt8K@nimes \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eblake@redhat.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).