bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Subject: get-rusage-data: Avoid test failure on NetBSD 9.3
Date: Thu, 18 Jan 2024 20:01:35 +0100	[thread overview]
Message-ID: <3366471.RL5eaSpR8r@nimes> (raw)

On NetBSD 9.3 (x86_64, arm64, powerpc) I see a test failure:

../../gltests/test-get-rusage-data.c:66: assertion 'value3 > value1' failed
FAIL test-get-rusage-data (exit status: 134)

This patch acknowledges the NetBSD behaviour, like the one on FreeBSD and
OpenBSD.


2024-01-18  Bruno Haible  <bruno@clisp.org>

	get-rusage-data: Avoid test failure on NetBSD 9.3.
	* tests/test-get-rusage-data.c (main): Don't expect a strict increase on
	NetBSD systems.

diff --git a/tests/test-get-rusage-data.c b/tests/test-get-rusage-data.c
index 29a68d7cc2..eab165ee01 100644
--- a/tests/test-get-rusage-data.c
+++ b/tests/test-get-rusage-data.c
@@ -61,7 +61,7 @@ main ()
       ASSERT (value2 >= value1);
       ASSERT (value3 >= value2);
 
-#if !(__GLIBC__ == 2 || MUSL_LIBC || (defined __APPLE__ && defined __MACH__) || defined __FreeBSD__ || defined __DragonFly__ || defined __OpenBSD__ || defined _WIN32 || defined __CYGWIN__)
+#if !(__GLIBC__ == 2 || MUSL_LIBC || (defined __APPLE__ && defined __MACH__) || defined __FreeBSD__ || defined __DragonFly__ || defined __NetBSD__ || defined __OpenBSD__ || defined _WIN32 || defined __CYGWIN__)
       /* Allocating 2.5 MB of memory should increase the data segment size.  */
       ASSERT (value3 > value1);
 #endif





                 reply	other threads:[~2024-01-18 19:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3366471.RL5eaSpR8r@nimes \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    /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).