bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
* get-rusage-data: Avoid test failure on NetBSD 9.3
@ 2024-01-18 19:01 Bruno Haible
  0 siblings, 0 replies; only message in thread
From: Bruno Haible @ 2024-01-18 19:01 UTC (permalink / raw)
  To: bug-gnulib

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





^ permalink raw reply related	[flat|nested] only message in thread

only message in thread, other threads:[~2024-01-18 19:01 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-01-18 19:01 get-rusage-data: Avoid test failure on NetBSD 9.3 Bruno Haible

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