From 54706e6557ffa2b81352a0028c8ffd297e2b9c17 Mon Sep 17 00:00:00 2001 From: Thomas Haller Date: Fri, 27 Oct 2017 11:15:51 +0200 Subject: [PATCH] tests: increase timeout for arping test I hit an assertion failure running with valgrind on a busy machine. Maybe the timeout is just not long enough for every case. Increase it. (cherry picked from commit 88c24ffc6aa8484310505726fd7e3010ef9c7c45) --- src/devices/tests/test-arping.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/devices/tests/test-arping.c b/src/devices/tests/test-arping.c index 59223f11fd..5857c26508 100644 --- a/src/devices/tests/test-arping.c +++ b/src/devices/tests/test-arping.c @@ -87,7 +87,7 @@ test_arping_common (test_fixture *fixture, TestInfo *info) g_signal_connect (manager, NM_ARPING_MANAGER_PROBE_TERMINATED, G_CALLBACK (arping_manager_probe_terminated), loop); g_assert (nm_arping_manager_start_probe (manager, 100, NULL)); - g_assert (nmtst_main_loop_run (loop, 1000)); + g_assert (nmtst_main_loop_run (loop, 2000)); for (i = 0; info->addresses[i]; i++) { g_assert_cmpint (nm_arping_manager_check_address (manager, info->addresses[i]),