haproxy/reg-tests/sample_fetches/tcpinfo_rtt.vtc
Willy Tarreau 48d5ef363d REGTESTS: restrict execution to a single thread group
When threads are enabled and running on a machine with multiple CCX
or multiple nodes, thread groups are now enabled since 3.3-dev2, causing
load-balancing algorithms to randomly fail due to incoming connections
spreading over multiple groups and using different load balancing indexes.

Let's just force "thread-groups 1" into all configs when threads are
enabled to avoid this.
2025-06-30 18:54:35 +02:00

44 lines
1010 B
Plaintext

varnishtest "Test declaration of TCP rtt fetches"
# feature cmd "$HAPROXY_PROGRAM -cc 'version_atleast(v2.8-dev8)'"
feature ignore_unknown_macro
server s1 {
rxreq
txresp
} -start
haproxy h1 -conf {
global
.if feature(THREAD)
thread-groups 1
.endif
defaults common
mode http
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
frontend fe from common
bind "fd@${feh1}"
default_backend be
backend be from common
http-response set-header x-test1 "%[fc_rtt]"
http-response set-header x-test2 "%[bc_rtt(us)]"
http-response set-header x-test3 "%[fc_rttvar]"
http-response set-header x-test4 "%[bc_rttvar]"
server s1 ${s1_addr}:${s1_port}
} -start
client c1 -connect ${h1_feh1_sock} {
txreq -req GET -url /
rxresp
expect resp.status == 200
expect resp.http.x-test2 ~ "[0-9]+"
} -run