haproxy/reg-tests/spoe/wrong_init.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

23 lines
639 B
Plaintext

# commit 84c844eb12b250aa86f2aadaff77c42dfc3cb619
# BUG/MINOR: spoe: Initialize variables used during conf parsing before any check
#
# Some initializations must be done at the beginning of parse_spoe_flt to avoid
# segmentation fault when first errors are caught, when the "filter spoe" line is
# parsed.
#REGTEST_TYPE=bug
varnishtest "SPOE bug: missing configuration file"
feature ignore_unknown_macro
haproxy h1 -conf-BAD {} {
defaults
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
frontend my-front
filter spoe
}