Re: [Tarantool-patches] [PATCH 0/2] gitlab-ci: increase testing timeouts

["Alexander V. Tikhonov" <avtikhon@tarantool.org>]

Hi Alexander, thanks for the patch, as I see no new degradation found in
gitlab-ci testing commit criteria pipeline [1], patch LGTM.

[1] - https://gitlab.com/tarantool/tarantool/-/pipelines/234706924

On Sun, Dec 27, 2020 at 07:13:24AM +0300, Alexander Turenko wrote:
> The first commit allows to pass any variable from current environment to
> a docker container or a ssh session with a virtualbox machine. The
> second brings test-run support for setting custom timeouts via
> environment variables.
> 
> I set ~300 seconds timeouts in the GitLab CI web interface.
> 
> The main reason to increase the timeouts is stalls of disk accesses when
> many vinyl tests are run in parallel and amount of machine resources we
> have at the moment.
> 
> See details in the commit messages.
> 
> I looked over all jobs and, where we run testing, test-run sets the
> increased timeouts.
> 
> https://github.com/tarantool/tarantool/tree/Totktonada/gitlab-ci-increase-testing-timeouts
> https://github.com/tarantool/test-run/issues/258
> 
> Alexander Turenko (2):
>   ci: preserve certain environment variables
>   test: update test-run (pass timeouts via env)
> 
>  .gitlab.mk | 14 +++++++++++---
>  .travis.mk | 22 ++++++++++++++++++++--
>  test-run   |  2 +-
>  3 files changed, 32 insertions(+), 6 deletions(-)
> 
> -- 
> 2.25.0
>