ci: fix failed tests #931

oleg-jukovec · 2024-08-28T18:53:15Z

There are currently 3-4 failed CI tests. We need to fix them.

There are a few failed tests with replacing tarantool sdk version in CI workflow from 3.0.0 into 3.2.0. After the patch all failed tests related with the upgrade was fixed. Part of #931

There was problem with installation in previous tarantool 3.0.0 skd version. After the patch the version was upgraded to the newest one. Part of #931

There was a problem with rocks installation using `tt rocks install` in test where tarantool doesn't exist in PATH. It was `mysql` rock which had problems with building on system. After the patch rock was replaced on `psql` (PostreSQL connector) due to we test installation without `tarantool` in PATH and it is doesn't matter which package we install. Part of #931

There was a problem in `TestInstanceLogger` test with the fact that cleanup after the test recieves error `io: read/write on closed pipe`. After the patch the order of pipes closing was updated by moving it to the cleanup block. A check was also added to send a SIGKILL signal to the process if it is alive, to avoid the `sending a signal to a killed process` error. Part of #931

After updating tarantool sdk version to the 3.2.0 stopping instance in `test_running_env_variables` causes an error with cleaning all logs in json format that was written before. So it wasn't possible to determine json format after stopping instance. After the patch the order of distructing tarantool was moved to the special `finally` block. Determination of json format was also updated with `wait_string_in_file` function with special timeout. Part of #931

There was problem with installation in previous tarantool 3.0.0 sdk version. After the patch the version was upgraded to the newest one. Part of #931

There was a problem with rocks installation using `tt rocks install` in test where tarantool doesn't exist in PATH. It was `mysql` rock which had problems with building on system. After the patch rock was replaced on `psql` (PostreSQL connector) due to we test installation without `tarantool` in PATH and it is doesn't matter which package we install. Part of #931

There was a problem in `TestInstanceLogger` test with the fact that cleanup after the test recieves error `io: read/write on closed pipe`. After the patch the order of pipes closing was updated by moving it to the cleanup block. A check was also added to send a SIGKILL signal to the process if it is alive, to avoid the `sending a signal to a killed process` error. Part of #931

After updating tarantool sdk version to the 3.2.0 stopping instance in `test_running_env_variables` causes an error with cleaning all logs in json format that was written before. So it wasn't possible to determine json format after stopping instance. After the patch the order of distructing tarantool was moved to the special `finally` block. Determination of json format was also updated with `wait_string_in_file` function with special timeout. Part of #931

There was problem with installation in previous tarantool 3.0.0 sdk version. After the patch the version was upgraded to the newest one. Part of #931

There was a problem with rocks installation using `tt rocks install` in test where tarantool doesn't exist in PATH. It was `mysql` rock which had problems with building on system. After the patch rock was replaced on `psql` (PostreSQL connector) due to we test installation without `tarantool` in PATH and it is doesn't matter which package we install. Part of #931

There was a problem in `TestInstanceLogger` test with the fact that cleanup after the test recieves error `io: read/write on closed pipe`. After the patch the order of pipes closing was updated by moving it to the cleanup block. A check was also added to send a SIGKILL signal to the process if it is alive, to avoid the `sending a signal to a killed process` error. Part of #931

After updating tarantool sdk version to the 3.2.0 stopping instance in `test_running_env_variables` causes an error with cleaning all logs in json format that was written before. So it wasn't possible to determine json format after stopping instance. After the patch the order of distructing tarantool was moved to the special `finally` block. Determination of json format was also updated with `wait_string_in_file` function with special timeout. Part of #931

There were a lot of problems related with docker runtime on macOS, so the tests on it always fail. After the patch `colima` (container runtime for macos) was added to CI pipeline. Closes #931

Sometimes CI on macos fails with an error "docker daemon not running". To avoid it after the patch docker socket is provided in the github env directly. Part of #931