The -W mode implemented in VTest is not reliable anymore, because VTest
waits for the pidfile to be created. But with the new master-worker
mode, this file is created long before haproxy is ready. This can lead
to the test being started too soon, and failing from time to time.
The -Ws option allows to wait for haproxy to deliver a message to VTest
once it is ready.
feature ignore_unknown_macro
-haproxy h1 -W -conf {
+haproxy h1 -Ws -conf {
defaults
timeout client 30s
timeout server 30s
txresp
} -repeat 2 -start
-haproxy h1 -W -S -conf {
+haproxy h1 -Ws -S -conf {
defaults
mode http
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
} -start
-haproxy h1 -W -S -conf {
+haproxy h1 -Ws -S -conf {
global
log ${S1_addr}:${S1_port} local0 info
server s1 {
} -start
-haproxy h1 -W -S -conf {
+haproxy h1 -Ws -S -conf {
defaults
mode http
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
server s1 {
} -start
-haproxy h1 -W -S -conf {
+haproxy h1 -Ws -S -conf {
global
expose-deprecated-directives
defaults
#EXCLUDE_TARGETS=freebsd,osx,generic
#REGTEST_TYPE=devel
-haproxy h1 -W -S -conf {
+haproxy h1 -Ws -S -conf {
global
stats socket "${tmpdir}/h1/stats" level admin expose-fd listeners
#EXCLUDE_TARGETS=freebsd,osx,generic
#REGTEST_TYPE=devel
-haproxy h1 -W -S -conf {
+haproxy h1 -Ws -S -conf {
global
stats socket "${tmpdir}/h1/stats" level admin expose-fd listeners