RepoMirrors
/
haproxy
mirror of http://git.haproxy.org/git/haproxy.git/
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
haproxy/reg-tests/lua/txn_get_priv-thread.vtc

75 lines
1.6 KiB
Plaintext
Raw Normal View History

REGTESTS: add a test for the threaded Lua code This is simply txn_get_priv.vtc with the loading made using lua-load-per-thread, allowing all threads to run independently. There's nothing global nor thread-specific in this test, which makes an excellent example of something that should work out of the box. Four concurrent clients are initialized with 4 loops each so as to give a little chance to various threads to run concurrently.
2020-12-02 15:44:34 +00:00
varnishtest "Lua: txn:get_priv() scope"
#REQUIRE_OPTIONS=LUA,OPENSSL
#REQUIRE_VERSION=2.4
#REGTEST_TYPE=bug
feature ignore_unknown_macro
REGTESTS: use -dW by default on every reg-tests Every reg-test now runs without any warning, so let's acivate -dW by default so the new ones will inheritate the option. This patch reverts 9d511b3c ("REGTESTS: enable -dW on almost all tests to fail on warnings") and adds -dW in the default HAPROXY_ARGS of scripts/run-regtests.sh instead.
2024-11-19 15:51:30 +00:00
haproxy h1 -conf {
REGTESTS: add a test for the threaded Lua code This is simply txn_get_priv.vtc with the loading made using lua-load-per-thread, allowing all threads to run independently. There's nothing global nor thread-specific in this test, which makes an excellent example of something that should work out of the box. Four concurrent clients are initialized with 4 loops each so as to give a little chance to various threads to run concurrently.
2020-12-02 15:44:34 +00:00
global
REGTESTS: disable inter-thread idle connection sharing on sensitive tests Some regtests involve multiple requests from multiple clients, which can be dispatched as multiple requests to a server. It turns out that the idle connection sharing works so well that very quickly few connections are used, and regularly some of the remaining idle server connections time out at the moment they were going to be reused, causing those random "HTTP header incomplete" traces in the logs that make them fail often. In the end this is only an artefact of the test environment. And indeed, some tests like normalize-uri which perform a lot of reuse fail very often, about 20-30% of the times in the CI, and 100% of the time in local when running 1000 tests in a row. Others like ubase64, sample_fetches or vary_* fail less often but still a lot in tests. This patch addresses this by adding "tune.idle-pool.shared off" to all tests which have at least twice as many requests as clients. It proves very effective as no single error happens on normalize-uri anymore after 10000 tests. Also 100 full runs of all tests yield no error anymore. One test is tricky, http_abortonclose, it used to fail ~10 times per 1000 runs and with this workaround still fails once every 1000 runs. But the test is complex and there's a warning in it mentioning a possible issue when run in parallel due to a port reuse.
2021-05-09 12:41:41 +00:00
# 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
REGTESTS: add a test for the threaded Lua code This is simply txn_get_priv.vtc with the loading made using lua-load-per-thread, allowing all threads to run independently. There's nothing global nor thread-specific in this test, which makes an excellent example of something that should work out of the box. Four concurrent clients are initialized with 4 loops each so as to give a little chance to various threads to run concurrently.
2020-12-02 15:44:34 +00:00
lua-load-per-thread ${testdir}/txn_get_priv.lua
lua-load-per-thread ${testdir}/txn_get_priv-print_r.lua
REGTESTS: add missing timeouts to 30 tests No less than 30 tests were missing timeouts, preventing them from being started with zero-warning. Since they were not supposed to trigger, they have been set to 30s so as never to trigger, and now they do not produce any warning anymore.
2024-11-19 06:43:04 +00:00
defaults
timeout client 30s
timeout server 30s
timeout connect 30s
REGTESTS: add a test for the threaded Lua code This is simply txn_get_priv.vtc with the loading made using lua-load-per-thread, allowing all threads to run independently. There's nothing global nor thread-specific in this test, which makes an excellent example of something that should work out of the box. Four concurrent clients are initialized with 4 loops each so as to give a little chance to various threads to run concurrently.
2020-12-02 15:44:34 +00:00
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