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 2/2] test: update test-run (pass timeouts via env) Date: Sun, 27 Dec 2020 07:13:26 +0300 [thread overview] Message-ID: <45826a06fbf6e5b436a832cf0bd9491737ca6314.1609041893.git.alexander.turenko@tarantool.org> (raw) In-Reply-To: <cover.1609041893.git.alexander.turenko@tarantool.org> 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 --- test-run | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test-run b/test-run index 584e273b1..9e5fc6d0f 160000 --- a/test-run +++ b/test-run @@ -1 +1 @@ -Subproject commit 584e273b134ffa0ee7d44419f7443f752ff4fb33 +Subproject commit 9e5fc6d0fede3b1d142a44c3ca36cfff3cb32f9f -- 2.25.0
next prev parent 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 [Tarantool-patches] [PATCH 0/2] gitlab-ci: increase testing timeouts Alexander Turenko 2020-12-27 4:13 ` [Tarantool-patches] [PATCH 1/2] ci: preserve certain environment variables Alexander Turenko 2020-12-27 4:13 ` Alexander Turenko [this message] 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=45826a06fbf6e5b436a832cf0bd9491737ca6314.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 2/2] test: update test-run (pass timeouts via env)' \ /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