From: Alexander Turenko <alexander.turenko@tarantool.org>
To: "Alexander V . Tikhonov" <avtikhon@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org,
Alexander Turenko <alexander.turenko@tarantool.org>
Subject: [Tarantool-patches] [PATCH 0/2] gitlab-ci: increase testing timeouts
Date: Sun, 27 Dec 2020 07:13:24 +0300 [thread overview]
Message-ID: <cover.1609041893.git.alexander.turenko@tarantool.org> (raw)
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
next reply other threads:[~2020-12-27 4:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-27 4:13 Alexander Turenko [this message]
2020-12-27 4:13 ` [Tarantool-patches] [PATCH 1/2] ci: preserve certain environment variables Alexander Turenko
2020-12-27 4:13 ` [Tarantool-patches] [PATCH 2/2] test: update test-run (pass timeouts via env) Alexander Turenko
2020-12-27 4:37 ` [Tarantool-patches] [PATCH 0/2] gitlab-ci: increase testing timeouts Alexander V. Tikhonov
2020-12-27 5:22 ` Alexander Turenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1609041893.git.alexander.turenko@tarantool.org \
--to=alexander.turenko@tarantool.org \
--cc=avtikhon@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH 0/2] gitlab-ci: increase testing timeouts' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox