haproxy/reg-tests/checks/4be_1srv_smtpchk_httpchk_layer47errors.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

95 lines
2.6 KiB
Plaintext

varnishtest "Check: smptchk option"
feature ignore_unknown_macro
#EXCLUDE_TARGETS=freebsd,osx,generic
#REGTEST_TYPE=slow
barrier b cond 3
syslog S1 -level notice {
recv
expect ~ "[^:\\[ ]\\[${h1_pid}\\]: Health check for server be1/srv1 succeeded.+reason: Layer7 check passed.+code: 2(20|48).+check duration: [[:digit:]]+ms.+status: 1/1 UP."
barrier b sync
recv
expect ~ "Health check for server be1/srv1 failed.+reason: Layer7 timeout.+check duration: [[:digit:]]+ms.+status: 0/1 DOWN"
} -start
syslog S2 -level notice {
recv
expect ~ "[^:\\[ ]\\[${h1_pid}\\]: Health check for server be2/srv2 succeeded.+reason: Layer7 check passed.+code: 200.+.+check duration: [[:digit:]]+ms.+status: 1/1 UP."
barrier b sync
recv
expect ~ "[^:\\[ ]\\[${h1_pid}\\]: Health check for server be2/srv2 failed.+reason: Layer7 timeout.+check duration: [[:digit:]]+ms.+status: 0/1 DOWN"
} -start
syslog S3 -level notice {
recv
expect ~ "[^:\\[ ]\\[${h1_pid}\\]: Health check for server be3/srv3 failed.+reason: Layer4 connection problem.+info: \"General socket error \\(Network is unreachable\\)\".+check duration: [[:digit:]]+ms.+status: 0/1 DOWN."
} -start
syslog S4 -level notice {
recv
expect ~ "[^:\\[ ]\\[${h1_pid}\\]: Health check for server be4/srv4 failed.+reason: Layer4 connection problem.+info: \"Connection refused\".+check duration: [[:digit:]]+ms.+status: 0/1 DOWN."
} -start
server s1 {
send "2"
send "2"
send "0"
send "\r\n\r\n"
recv 16
send "2"
send "4"
send "8"
send "\r\n\r\n"
} -start
server s2 {
rxreq
txresp
} -start
haproxy h1 -conf {
defaults
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
option log-health-checks
default-server inter 200ms downinter 100ms rise 1 fall 1
backend be1
option smtpchk
log ${S1_addr}:${S1_port} daemon
server srv1 ${s1_addr}:${s1_port} check
backend be2
mode tcp
log ${S2_addr}:${S2_port} daemon
option httpchk OPTIONS * HTTP/1.1\r\nHost:\ www
server srv2 ${s2_addr}:${s2_port} check
backend be3
log ${S3_addr}:${S3_port} daemon
server srv3 255.255.255.255:11111 check
backend be4
log ${S4_addr}:${S4_port} daemon
server srv4 localhost:11111 check
} -start
haproxy h1 -cli {
barrier b sync
send "show servers state"
expect ~ .*
}
server s1 -wait
server s2 -wait
syslog S1 -wait
syslog S2 -wait
syslog S3 -wait
syslog S4 -wait