REGTESTS: peers: leave a bit more time to peers to synchronize

tls_basic_sync_wo_stkt_backend fails once every 200 runs for me. This
seems to be because the startup delay doesn't always allow peers to
perform a simultaneous connect, close and new attempt. With 3s I can't
see it fail anymore. In addition the long "delay 0.2" are still way too
much since we do not really care about the startup order in practice.

(cherry picked from commit c38200563645e314bd0af59958c75171cca59d4b)
Signed-off-by: Willy Tarreau <w@1wt.eu>

diff --git a/reg-tests/peers/tls_basic_sync_wo_stkt_backend.vtc b/reg-tests/peers/tls_basic_sync_wo_stkt_backend.vtc
index 44cd754..7e1bfd3 100644 (file)
--- a/reg-tests/peers/tls_basic_sync_wo_stkt_backend.vtc
+++ b/reg-tests/peers/tls_basic_sync_wo_stkt_backend.vtc
@@ -115,20 +115,20 @@ client c4 -connect ${h1_fe_sock} {
 } -start
 
 haproxy h1 -start
-delay 0.2
+delay 0.02
 haproxy h2 -start
-delay 0.2
+delay 0.02
 haproxy h3 -start
-delay 0.2
+delay 0.02
 haproxy h4 -start
-delay 0.2
+delay 0.02
 
 client c1 -wait
 client c2 -wait
 client c3 -wait
 client c4 -wait
 
-delay 2
+delay 3
 
 haproxy h1 -cli {
     send "show table peers/stkt"