haproxy/reg-tests/checks/tcp-check_min-recv.vtc
Willy Tarreau f673923629 REGTESTS: extend the default I/O timeouts and make them overridable
With the CI occasionally slowing down, we're starting to see again some
spurious failures despite the long 1-second timeouts. This reports false
positives that are disturbing and doesn't provide as much value as this
could. However at this delay it already becomes a pain for developers
to wait for the tests to complete.

This commit adds support for the new environment variable
HAPROXY_TEST_TIMEOUT that will allow anyone to modify the connect,
client and server timeouts. It was set to 5 seconds by default, which
should be plenty for quite some time in the CI. All relevant values
that were 200ms or above were replaced by this one. A few larger
values were left as they are special. One test for the set-timeout
action that used to rely on a fixed 1-sec value was extended to a
fixed 5-sec, as the timeout is normally not reached, but it needs
to be known to compare the old and new values.
2021-11-18 17:57:11 +01:00

69 lines
1.9 KiB
Plaintext

varnishtest "tcp-check negative bounded regex match"
#EXCLUDE_TARGETS=freebsd,osx,generic
#REGTEST_TYPE=slow
#REQUIRE_VERSION=2.2
# This test use a negative expect rule and verify that setting a required
# minimum amount of data to match.
feature ignore_unknown_macro
syslog S1 -level notice {
recv
expect ~ "[^:\\[ ]\\[${h1_pid}\\]: Health check for server be1/srv1 failed, reason: Layer7 timeout.*at step 2 of tcp-check"
} -start
syslog S2 -level notice {
recv
expect ~ "[^:\\[ ]\\[${h1_pid}\\]: Health check for server be2/srv1 succeeded"
} -start
server s1 {
send "valid"
delay 0.2
expect_close
} -start
server s2 {
send "valid"
recv 10
send "valid"
delay 0.2
expect_close
} -start
haproxy h1 -conf {
defaults
mode tcp
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
timeout check "${HAPROXY_TEST_TIMEOUT-5s}"
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
backend be1
# must fail fast
timeout check 1
timeout server 1
log ${S1_addr}:${S1_port} len 2048 local0
option tcp-check
option log-health-checks
tcp-check connect
tcp-check expect !rstring "^error" comment "negative check"
tcp-check expect string "valid" comment "positive check"
tcp-check send "0123456789"
tcp-check expect string "valid" comment "positive check"
server srv1 ${s1_addr}:${s1_port} check inter 200ms rise 1 fall 1
backend be2
log ${S2_addr}:${S2_port} len 2048 local0
option tcp-check
option log-health-checks
tcp-check connect
tcp-check expect min-recv 5 !rstring "^error" comment "negative check"
tcp-check expect string "valid" comment "positive check"
tcp-check send "0123456789"
tcp-check expect string "valid" comment "positive check"
server srv1 ${s2_addr}:${s2_port} check inter 200ms rise 1 fall 1
} -start
syslog S1 -wait
syslog S2 -wait