[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
nonblocking-socket-tests: Fix test failure on Android 4.3
From: |
Bruno Haible |
Subject: |
nonblocking-socket-tests: Fix test failure on Android 4.3 |
Date: |
Sat, 26 Jan 2019 18:56:00 +0100 |
User-agent: |
KMail/5.1.3 (Linux/4.4.0-141-generic; KDE/5.18.0; x86_64; ; ) |
On Android 4.3, I'm seeing this test failure:
FAIL: test-nonblocking-socket.sh
================================
main:1: spent_time = 0.051472, data_block_size too small
FAIL test-nonblocking-socket.sh (exit status: 1)
This patch fixes it.
2019-01-26 Bruno Haible <address@hidden>
nonblocking-socket-tests: Fix test failure on Android 4.3.
* tests/test-nonblocking-socket.h (SOCKET_HAS_LARGE_BUFFER): Define to 1
also on Android.
diff --git a/tests/test-nonblocking-socket.h b/tests/test-nonblocking-socket.h
index f049300..c3f9f54 100644
--- a/tests/test-nonblocking-socket.h
+++ b/tests/test-nonblocking-socket.h
@@ -21,6 +21,7 @@
Platform SOCKET_DATA_BLOCK_SIZE
Linux >= 7350000 (depends on circumstances)
+ Linux/Android >= 1700000 (approx.)
FreeBSD >= 107521
OpenBSD >= 106430 (depends on circumstances)
Mac OS X >= 680000 (depends on circumstances)
@@ -44,7 +45,7 @@
sockets have very large buffers in the kernel, so that write() calls
succeed before the reader has started reading, even if fd is blocking
and the amount of data is larger than 1 MB. */
-#if defined __linux__ || (defined __APPLE__ && defined __MACH__) || defined
_WIN32 || defined __CYGWIN__
+#if defined __linux__ || defined __ANDROID__ || (defined __APPLE__ && defined
__MACH__) || defined _WIN32 || defined __CYGWIN__
# define SOCKET_HAS_LARGE_BUFFER 1
#else
# define SOCKET_HAS_LARGE_BUFFER 0
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- nonblocking-socket-tests: Fix test failure on Android 4.3,
Bruno Haible <=