Increase the min hs timeout in one of the ssl_opt tests

This triggered some spurious CI failure, where
the network is flaky. Increasing the min value,
leaving the max at the same distance should 
account for this.
Signed-off-by: Andrzej Kurek <andrzej.kurek@arm.com>
This commit is contained in:
Andrzej Kurek 2021-01-14 06:17:40 -05:00
parent 5ef12c0cbc
commit 7ad75b6a22

View File

@ -7414,8 +7414,8 @@ not_with_valgrind # spurious resend
requires_config_disabled MBEDTLS_SSL_CONF_READ_TIMEOUT
requires_config_enabled MBEDTLS_SSL_DTLS_CLIENT_PORT_REUSE
run_test "DTLS client reconnect from same port: reference" \
"$P_SRV dtls=1 exchanges=2 read_timeout=20000 hs_timeout=10000-20000" \
"$P_CLI dtls=1 exchanges=2 debug_level=2 hs_timeout=10000-20000" \
"$P_SRV dtls=1 exchanges=2 read_timeout=20000 hs_timeout=15000-25000" \
"$P_CLI dtls=1 exchanges=2 debug_level=2 hs_timeout=15000-25000" \
0 \
-C "resend" \
-S "The operation timed out" \
@ -7425,7 +7425,7 @@ not_with_valgrind # spurious resend
requires_config_disabled MBEDTLS_SSL_CONF_READ_TIMEOUT
requires_config_enabled MBEDTLS_SSL_DTLS_CLIENT_PORT_REUSE
run_test "DTLS client reconnect from same port: reconnect" \
"$P_SRV dtls=1 exchanges=2 read_timeout=20000 hs_timeout=10000-20000" \
"$P_SRV dtls=1 exchanges=2 read_timeout=20000 hs_timeout=15000-25000" \
"$P_CLI dtls=1 exchanges=2 debug_level=2 hs_timeout=15000-25000 reconnect_hard=1" \
0 \
-C "resend" \