From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp59.i.mail.ru (smtp59.i.mail.ru [217.69.128.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id F1D934765E0 for ; Sun, 27 Dec 2020 07:13:14 +0300 (MSK) From: Alexander Turenko Date: Sun, 27 Dec 2020 07:13:24 +0300 Message-Id: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [Tarantool-patches] [PATCH 0/2] gitlab-ci: increase testing timeouts List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Alexander V . Tikhonov" Cc: tarantool-patches@dev.tarantool.org, Alexander Turenko 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