test: update test-run (pass timeouts via env)
The following variables now control timeouts (if corresponding command line options are not passed): TEST_TIMEOUT, NO_OUTPUT_TIMEOUT, REPLICATION_SYNC_TIMEOUT. See [1] for details. I set the following values in the GitLab CI web interface: | Variable | Value | | ------------------------ | ------------------------------------------------------- | | REPLICATION_SYNC_TIMEOUT | 300 | | TEST_TIMEOUT | 310 | | NO_OUTPUT_TIMEOUT | 320 | | PRESERVE_ENVVARS | REPLICATION_SYNC_TIMEOUT,TEST_TIMEOUT,NO_OUTPUT_TIMEOUT | See packpack change [2] and the commit 'ci: preserve certain environment variables' regarding the PRESERVE_ENVVARS variable. The reason, why we need to increase timeouts, comes from the following facts: - We use self-hosted runners to serve GitLab CI jobs. So, the machine resources are limited. - We run testing with high level of parallelism to speed it up. - We have a bunch of vinyl tests, which intensively use disk. Disk accesses may be quite long within this infrastructure and the obvious way to workaround the problem is to increase timeouts. In the long term we should scale resources depending on the testing needs. We'll try to use GitHub hosted runners or, if we'll reach some limits, will setup GitHub runners on the Mail.Ru Cloud Solutions infrastructure. [1]: https://github.com/tarantool/test-run/issues/258 [2]: https://github.com/packpack/packpack/pull/135
Please register or sign in to comment