haproxy/reg-tests/lua/lua_socket.vtc

varnishtest "Lua: check socket functionality from a lua-task"
feature ignore_unknown_macro

#REQUIRE_OPTIONS=LUA

server s1 {
    rxreq
    txresp -bodylen 20
} -start

haproxy h1 -conf {
    global
    .if feature(THREAD)
        thread-groups 1
    .endif

        tune.lua.bool-sample-conversion normal
        lua-load ${testdir}/lua_socket.lua

    defaults
        timeout client 30s
        timeout server 30s
        timeout connect 30s

    frontend fe1
        mode http
        bind "fd@${fe1}"
        default_backend b1

    backend b1
        mode http
        http-request use-service lua.fakeserv

} -start

client c0 -connect ${h1_fe1_sock} {
    txreq -url "/" -hdr "vtcport: ${s1_port}"
    rxresp
    expect resp.status == 200
} -run


server s1 -wait
REGTEST: lua: check socket functionality from a lua-task Adding a new test /reg-tests/lua/b00004.vtc which checks if the core.tcp() socket basic functions properly when used from a lua-task 2018-11-30 15:01:01 -05:00			`varnishtest "Lua: check socket functionality from a lua-task"`
			`feature ignore_unknown_macro`

			`#REQUIRE_OPTIONS=LUA`

			`server s1 {`
			`rxreq`
			`txresp -bodylen 20`
			`} -start`

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 10:51:30 -05:00			`haproxy h1 -conf {`
REGTEST: lua: check socket functionality from a lua-task Adding a new test /reg-tests/lua/b00004.vtc which checks if the core.tcp() socket basic functions properly when used from a lua-task 2018-11-30 15:01:01 -05:00			`global`
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 12:44:07 -04:00			`.if feature(THREAD)`
			`thread-groups 1`
			`.endif`

MINOR: hlua: rename "tune.lua.preserve-smp-bool" to "tune.lua.bool-sample-conversion" A better name was found for the option implemented in ec74438 ("MINOR: hlua: add option to preserve bool type from smp to lua") Indeed, "tune.lua.preserve-smp-bool {on \| off}" wasn't explicit enough nor did it encourage the adoption of the new "fixed" behavior (vs historical behavior which is now considered as a bug). Thus it becomes "tune.lua.bool-sample-conversion { normal \| pre-3.1-bug }" which actively encourage users to switch the new behavior after having patched in-use Lua script if needed. From a technical point of view, the logic remains the same, as the option currently defaults to "pre-3.1-bug" to prevent script breakage, and a warning is emitted if the option isn't set explicily and Lua is used. Documentation and regtests were updated. Must be backported in 3.1 with ec74438 and f2838f5 ("REGTESTS: fix lua-based regtests using tune.lua.smp-preserve-bool") 2024-12-20 11:25:29 -05:00			`tune.lua.bool-sample-conversion normal`
REGTEST: adapt some reg tests after renaming. Some reg tests and their dependencies have been renamed. They may be referenced by the .vtc files. So, this patch modifies also the references to these dependencies. 2019-03-29 11:13:48 -04:00			`lua-load ${testdir}/lua_socket.lua`
REGTEST: lua: check socket functionality from a lua-task Adding a new test /reg-tests/lua/b00004.vtc which checks if the core.tcp() socket basic functions properly when used from a lua-task 2018-11-30 15:01:01 -05:00
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 01:43:04 -05:00			`defaults`
			`timeout client 30s`
			`timeout server 30s`
			`timeout connect 30s`

REGTEST: lua: check socket functionality from a lua-task Adding a new test /reg-tests/lua/b00004.vtc which checks if the core.tcp() socket basic functions properly when used from a lua-task 2018-11-30 15:01:01 -05:00			`frontend fe1`
			`mode http`
			`bind "fd@${fe1}"`
			`default_backend b1`

			`backend b1`
			`mode http`
			`http-request use-service lua.fakeserv`

			`} -start`

			`client c0 -connect ${h1_fe1_sock} {`
			`txreq -url "/" -hdr "vtcport: ${s1_port}"`
			`rxresp`
			`expect resp.status == 200`
			`} -run`


REGTEST: fix the Lua test file name in test lua/h00002 :-) The file was moved but the lua file was not renamed in the VTC, leading to a failure when launched from a clean tree. 2018-12-07 09:25:26 -05:00			`server s1 -wait`