From 97151cce4ec45198431932b535170f4bde373f8e Mon Sep 17 00:00:00 2001 From: stevenhorsman Date: Thu, 6 Mar 2025 15:46:12 +0000 Subject: [PATCH] metrics: Improve iperf timeout The kubectl wait has a built in timeout of 30s, so wrapping it in waitForProcess, means we have 180/2 * 30 delay, which is much longer than intended, so just set the timeout directly. Signed-off-by: stevenhorsman --- .../network/iperf3_kubernetes/k8s-network-metrics-iperf3.sh | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/tests/metrics/network/iperf3_kubernetes/k8s-network-metrics-iperf3.sh b/tests/metrics/network/iperf3_kubernetes/k8s-network-metrics-iperf3.sh index 696be2f035..d0f7fc009b 100755 --- a/tests/metrics/network/iperf3_kubernetes/k8s-network-metrics-iperf3.sh +++ b/tests/metrics/network/iperf3_kubernetes/k8s-network-metrics-iperf3.sh @@ -186,8 +186,7 @@ function iperf3_start_deployment() { kubectl create -f "${IPERF_DEPLOYMENT}" # Check deployment creation - local cmd="kubectl wait --for=condition=Available deployment/iperf3-server-deployment" - waitForProcess "${wait_time}" "${sleep_time}" "${cmd}" + local cmd="kubectl wait --for=condition=Available deployment/iperf3-server-deployment --timeout=${wait_time}s" # Create DaemonSet kubectl create -f "${IPERF_DAEMONSET}"