Valentine Krasnobaeva 5bbcdc003a 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 22:00:58 +02:00
..
mcli_debug_dev.vtc	REGTESTS: cli: add delay 0.1 before connect to cli	2024-10-16 22:00:58 +02:00
mcli_show_info.vtc	REGTESTS: cli: add delay 0.1 before connect to cli	2024-10-16 22:00:58 +02:00
mcli_start_progs.vtc	REGTESTS: cli: add delay 0.1 before connect to cli	2024-10-16 22:00:58 +02:00