haproxy/reg-tests/lua/txn_get_priv-thread.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

80 lines
1.6 KiB
Plaintext

varnishtest "Lua: txn:get_priv() scope"
#REQUIRE_OPTIONS=LUA,OPENSSL
#REGTEST_TYPE=bug
feature ignore_unknown_macro
haproxy h1 -conf {
global
.if feature(THREAD)
thread-groups 1
.endif
# WT: limit false-positives causing "HTTP header incomplete" due to
# idle server connections being randomly used and randomly expiring
# under us.
tune.idle-pool.shared off
tune.lua.bool-sample-conversion normal
lua-load-per-thread ${testdir}/txn_get_priv.lua
lua-load-per-thread ${testdir}/txn_get_priv-print_r.lua
defaults
timeout client 30s
timeout server 30s
timeout connect 30s
frontend fe1
mode http
bind "fd@${fe1}"
default_backend b1
frontend fe2
mode http
bind ":8443" ssl crt ${testdir}/common.pem
stats enable
stats uri /
backend b1
mode http
http-request use-service lua.fakeserv
} -start
client c0 -repeat 4 -connect ${h1_fe1_sock} {
txreq -url "/0"
rxresp
expect resp.status == 200
txreq -url "/0"
rxresp
expect resp.status == 200
} -run
client c1 -repeat 4 -connect ${h1_fe1_sock} {
txreq -url "/1"
rxresp
expect resp.status == 200
txreq -url "/1"
rxresp
expect resp.status == 200
} -run
client c2 -repeat 4 -connect ${h1_fe1_sock} {
txreq -url "/2"
rxresp
expect resp.status == 200
txreq -url "/2"
rxresp
expect resp.status == 200
} -run
client c3 -repeat 4 -connect ${h1_fe1_sock} {
txreq -url "/3"
rxresp
expect resp.status == 200
txreq -url "/3"
rxresp
expect resp.status == 200
} -run