haproxy/reg-tests/mcli/mcli_start_progs.vtc

varnishtest "Try to start a master CLI with 2 programs"
#REGTEST_TYPE=bug
#REQUIRE_VERSION=2.0
feature cmd "command -v sleep"

feature ignore_unknown_macro

# Do nothing. Is there only to create s1_* macros
server s1 {
} -start

haproxy h1 -W -S -conf {
    defaults
        mode http
        timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
        timeout client  "${HAPROXY_TEST_TIMEOUT-5s}"
        timeout server  "${HAPROXY_TEST_TIMEOUT-5s}"

    frontend myfrontend
        bind "fd@${my_fe}"
        default_backend test

    backend test
        server www1 ${s1_addr}:${s1_port}

    program foo
        command sleep 10

    program bar
        command sleep 10

} -start

haproxy h1 -mcli {
    send "show proc"
    expect ~ ".*foo.*\n.*bar.*\n"
} -wait
REGTEST: mcli/mcli_start_progs: start 2 programs This regtest tests the issue #446 by starting 2 programs and checking if they exist in the "show proc" of the master CLI. Should be backported as far as 2.0. 2020-01-14 14:38:43 +00:00			`varnishtest "Try to start a master CLI with 2 programs"`
			`#REGTEST_TYPE=bug`
			`#REQUIRE_VERSION=2.0`
REGTESTS: Replace REQUIRE_BINARIES with 'command -v' This migrates the tests to the native `feature cmd` functionality of VTest. 2021-06-11 17:56:17 +00:00			`feature cmd "command -v sleep"`
REGTEST: mcli/mcli_start_progs: start 2 programs This regtest tests the issue #446 by starting 2 programs and checking if they exist in the "show proc" of the master CLI. Should be backported as far as 2.0. 2020-01-14 14:38:43 +00:00
			`feature ignore_unknown_macro`

			`# Do nothing. Is there only to create s1_* macros`
			`server s1 {`
			`} -start`

			`haproxy h1 -W -S -conf {`
			`defaults`
			`mode http`
REGTESTS: extend the default I/O timeouts and make them overridable With the CI occasionally slowing down, we're starting to see again some spurious failures despite the long 1-second timeouts. This reports false positives that are disturbing and doesn't provide as much value as this could. However at this delay it already becomes a pain for developers to wait for the tests to complete. This commit adds support for the new environment variable HAPROXY_TEST_TIMEOUT that will allow anyone to modify the connect, client and server timeouts. It was set to 5 seconds by default, which should be plenty for quite some time in the CI. All relevant values that were 200ms or above were replaced by this one. A few larger values were left as they are special. One test for the set-timeout action that used to rely on a fixed 1-sec value was extended to a fixed 5-sec, as the timeout is normally not reached, but it needs to be known to compare the old and new values. 2021-11-18 16:46:22 +00:00			`timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"`
			`timeout client "${HAPROXY_TEST_TIMEOUT-5s}"`
			`timeout server "${HAPROXY_TEST_TIMEOUT-5s}"`
REGTEST: mcli/mcli_start_progs: start 2 programs This regtest tests the issue #446 by starting 2 programs and checking if they exist in the "show proc" of the master CLI. Should be backported as far as 2.0. 2020-01-14 14:38:43 +00:00
			`frontend myfrontend`
			`bind "fd@${my_fe}"`
			`default_backend test`

			`backend test`
			`server www1 ${s1_addr}:${s1_port}`

			`program foo`
			`command sleep 10`

			`program bar`
			`command sleep 10`

			`} -start`

			`haproxy h1 -mcli {`
			`send "show proc"`
			`expect ~ ".foo.\n.bar.\n"`
			`} -wait`