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/mcli/mcli_start_progs.vtc

41 lines
825 B
Plaintext
Raw Normal View History

REGTESTS: disable temporarly mworker test on OSX -Ws on VTest is not working correctly for an unknown reason, the polling of the NOTIFY_SOCKET seems to timeout, and VTest never receives the READY message. This patch disables the reg-tests using -Ws on OS X.
2024-11-20 16:07:36 +00:00
#EXCLUDE_TARGETS=osx
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
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
REGTESTS: switch to -Ws for master-worker reg-tests 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.
2024-11-20 09:57:42 +00:00
haproxy h1 -Ws -S -conf {
BUG/MINOR: mworker-prog: don't warn about deprecated section with expose-deprecated-directives As master parses now expose-deprecated-directives option, let's emit warning about deprecated 'progam' section only in case, if this option wasn't set in the 'global' section. This allows to people, who don't prefer to remove the 'program' section immediately to continue to start the process in zero-warning mode. Adjust the warning message accordingly and mcli_start_progs.vtc test. As expose-deprecated-directives option is a 'global' section keyword, this section must always precede any 'program' section, if users still continue to keep 'program' section. This doesn't need to be backported, as related to the latest changes in the master-worker architecture.
2024-11-19 09:32:28 +00:00
global
expose-deprecated-directives
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
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 {
REGTESTS: cli: add delay 0.1 before connect to cli When vtest starts haproxy process, it loops until the moment, when haproxy pidfile is created. When pidfile is created, vtest considers that haproxy process is ready and it starts to perform test commands, in particular, it connects to CLI. It's not very reliable approach to base the check of the process readiness on the PID file. After master-worker architecture refactoring pidfile is created in the early init stage, but master and worker are not yet finished its initialization routines. So, all mcli tests and some tests where we sent commands to CLI start to fail regularly. In vtest at the moment there is no any other approach to check that the process is really ready. So let's add a delay 0.1s before connecting to CLI in all mcli tests and in acl_cli_spaces test.
2024-10-16 16:27:30 +00:00
delay 0.1
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
send "show proc"
expect ~ ".*foo.*\n.*bar.*\n"
} -wait