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

41 lines
928 B
Plaintext

varnishtest "Abstract unix socket - zero terminated"
feature ignore_unknown_macro
feature cmd "command -v curl"
# abns@ sockets are not available on freebsd
#EXCLUDE_TARGETS=freebsd,osx,generic
#REGTEST_TYPE=devel
haproxy h1 -Ws -S -conf {
global
.if feature(THREAD)
thread-groups 1
.endif
stats socket "${tmpdir}/h1/stats" level admin expose-fd listeners
defaults
mode http
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
listen testme
bind "fd@${testme}"
server f2 abnsz@hap-f2
frontend f2
bind abnsz@hap-f2
http-request return status 200 content-type text/plain string "ok"
} -start
client c1 -connect ${h1_testme_sock} {
txreq -url "/"
rxresp
expect resp.status == 200
} -run
shell {
curl -sfS --abstract-unix-socket hap-f2 "http://host/" | grep "ok"
}