From: Ralf Lici <[email protected]>

The second stage of test.sh ("run baseline data traffic") performs a
basic connectivity check with ping -qfc 500 -w 3.  On slower CI
instances this is too strict for TCP: the RTT is high enough that 500
echo requests do not reliably complete within 3 seconds, so the stage
flakes and the test fails even though the ovpn setup is healthy.

Reduce the packet count to 100 for both the plain and 3000-byte pings in
that stage.  This still verifies peer setup, key exchange, routing, and
data-path traffic, without making the basic connectivity check depend on
timing out under load.

Fixes: 959bc330a439 ("testing/selftests: add test tool and scripts for ovpn 
module")
Signed-off-by: Ralf Lici <[email protected]>
Signed-off-by: Antonio Quartulli <[email protected]>
---
 tools/testing/selftests/net/ovpn/test.sh | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tools/testing/selftests/net/ovpn/test.sh 
b/tools/testing/selftests/net/ovpn/test.sh
index b50dbe45a4d0..c06e3135fbef 100755
--- a/tools/testing/selftests/net/ovpn/test.sh
+++ b/tools/testing/selftests/net/ovpn/test.sh
@@ -98,10 +98,10 @@ ovpn_run_basic_traffic() {
                sleep 0.3
                ovpn_cmd_ok "send baseline traffic to peer ${p}" \
                        ip netns exec ovpn_peer0 \
-                       ping -qfc 500 -w 3 5.5.5.$((p + 1))
+                       ping -qfc 100 -w 3 5.5.5.$((p + 1))
                ovpn_cmd_ok "send large-payload traffic to peer ${p}" \
                        ip netns exec ovpn_peer0 \
-                       ping -qfc 500 -s 3000 -w 3 5.5.5.$((p + 1))
+                       ping -qfc 100 -s 3000 -w 3 5.5.5.$((p + 1))
 
                wait "${tcpdump_pid1}" || return 1
                wait "${tcpdump_pid2}" || return 1
-- 
2.53.0


Reply via email to