f673923629
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.
34 lines
821 B
Plaintext
34 lines
821 B
Plaintext
varnishtest "Set server FQDN via CLI crash"
|
|
|
|
feature ignore_unknown_macro
|
|
|
|
# for "set server <srv> fqdn"
|
|
#REQUIRE_VERSION=1.8
|
|
#REGTEST_TYPE=bug
|
|
|
|
# Do nothing. Is there only to create s1_* macros
|
|
server s1 {
|
|
} -start
|
|
|
|
haproxy h1 -conf {
|
|
defaults
|
|
mode http
|
|
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
|
|
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
|
|
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
|
|
|
|
frontend myfrontend
|
|
bind "fd@${my_fe}"
|
|
default_backend test
|
|
|
|
backend test
|
|
server www1 ${s1_addr}:${s1_port}
|
|
} -start
|
|
|
|
haproxy h1 -cli {
|
|
send "set server test/www1 fqdn foo.fqdn"
|
|
expect ~ "set server <b>/<s> fqdn failed because no resolution is configured."
|
|
send "show servers state test"
|
|
expect ~ "test 1 www1 ${s1_addr} .* - ${s1_port}"
|
|
} -wait
|