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_show_info.vtc

30 lines
631 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
MAJOR: config: remove parsing of the global "nbproc" directive This one was deprecated in 2.3 and marked for removal in 2.5. It suffers too many limitations compared to threads, and prevents some improvements from being engaged. Instead of a bypassable startup error, there is now a hard error. The parsing code was removed, and very few obvious cases were as well. The code is deeply rooted at certain places (e.g. "for" loops iterating from 0 to nbproc) so it will not be that trivial to remove everywhere. The "bind" and "bind-process" parsers will have to be adjusted, though maybe not completely changed if we later want to support thread groups for large NUMA machines. Some stats socket restrictions were removed, and the doc was updated according to what was done. A few places in the doc still refer to nbproc and will have to be revisited. The master-worker code also refers to the process number to distinguish between master and workers and will have to be carefully adjusted. The MAX_PROCS macro was reset to 1, this will at least reduce the size of some remaining arrays. Two regtests were dependieng on this directive, one with an explicit "nbproc 1" and another one testing the master's CLI using nbproc 4. Both were adapted.
2021-06-11 14:50:29 +00:00
varnishtest "Show info of process 1"
REGTEST: mcli/mcli_show_info: launch a 'show info' on the master CLI This test launches a HAProxy process in master worker with 'nbproc 4'. It sends a "show info" to the process 3 and verify that the right process replied. This regtest depends on the support of the master CLI for VTest.
2019-10-01 15:53:58 +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 {
REGTEST: mcli/mcli_show_info: launch a 'show info' on the master CLI This test launches a HAProxy process in master worker with 'nbproc 4'. It sends a "show info" to the process 3 and verify that the right process replied. This regtest depends on the support of the master CLI for VTest.
2019-10-01 15:53:58 +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_show_info: launch a 'show info' on the master CLI This test launches a HAProxy process in master worker with 'nbproc 4'. It sends a "show info" to the process 3 and verify that the right process replied. This regtest depends on the support of the master CLI for VTest.
2019-10-01 15:53:58 +00:00
frontend myfrontend
bind "fd@${my_fe}"
default_backend test
backend test
server www1 ${s1_addr}:${s1_port}
} -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
MAJOR: config: remove parsing of the global "nbproc" directive This one was deprecated in 2.3 and marked for removal in 2.5. It suffers too many limitations compared to threads, and prevents some improvements from being engaged. Instead of a bypassable startup error, there is now a hard error. The parsing code was removed, and very few obvious cases were as well. The code is deeply rooted at certain places (e.g. "for" loops iterating from 0 to nbproc) so it will not be that trivial to remove everywhere. The "bind" and "bind-process" parsers will have to be adjusted, though maybe not completely changed if we later want to support thread groups for large NUMA machines. Some stats socket restrictions were removed, and the doc was updated according to what was done. A few places in the doc still refer to nbproc and will have to be revisited. The master-worker code also refers to the process number to distinguish between master and workers and will have to be carefully adjusted. The MAX_PROCS macro was reset to 1, this will at least reduce the size of some remaining arrays. Two regtests were dependieng on this directive, one with an explicit "nbproc 1" and another one testing the master's CLI using nbproc 4. Both were adapted.
2021-06-11 14:50:29 +00:00
send "@1 show info"
expect ~ ".*\nProcess_num: 1\n.*"
REGTEST: mcli/mcli_show_info: launch a 'show info' on the master CLI This test launches a HAProxy process in master worker with 'nbproc 4'. It sends a "show info" to the process 3 and verify that the right process replied. This regtest depends on the support of the master CLI for VTest.
2019-10-01 15:53:58 +00:00
} -wait