From 053ee5fbb75099704c085c3fb23536b22c42d324 Mon Sep 17 00:00:00 2001 From: Andre Puschmann Date: Wed, 15 Jul 2020 10:54:46 +0200 Subject: [PATCH] iperf3: increase additional wait time for iperf client we've noticed that the Iperf client times out too soon in some experiment. It seems that this happens with ZMQ if the RAT is too slow (slower than realtime) and the eNB buffers too much data. This causes iperf to still receive DL data for example long after the configured runtime. Change-Id: I9b823ab22812c96920d54fb7342c8d4c578d5270 --- src/osmo_gsm_tester/obj/iperf3.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/osmo_gsm_tester/obj/iperf3.py b/src/osmo_gsm_tester/obj/iperf3.py index 252c55a5..2039a9ba 100644 --- a/src/osmo_gsm_tester/obj/iperf3.py +++ b/src/osmo_gsm_tester/obj/iperf3.py @@ -277,7 +277,7 @@ class IPerf3Client(log.Origin): proc = self.prepare_test_proc_locally(netns, popen_args) else: proc = self.prepare_test_proc_remotely(netns, popen_args) - proc.set_default_wait_timeout(time_sec + 30) # leave 30 extra sec for remote run, ctrl conn establishment, etc. + proc.set_default_wait_timeout(time_sec + 120) # leave extra time for remote run, ctrl conn establishment, buffer draining, etc. return proc def prepare_test_proc_remotely(self, netns, popen_args):