Tarantool development patches archive
 help / color / mirror / Atom feed
From: Alexander Turenko <alexander.turenko@tarantool.org>
To: "Alexander V. Tikhonov" <avtikhon@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH v6 0/2] Enable GitLab CI testing
Date: Thu, 4 Jul 2019 22:47:34 +0300	[thread overview]
Message-ID: <20190704194734.guyyzlcdhrfapei3@tkn_work_nb> (raw)
In-Reply-To: <cover.1561481610.git.avtikhon@tarantool.org>

Pushed to master and 2.1.

1.10 needs more commits from master around tests and CI to be
cherry-picked to apply the patch re gitlab-ci cleanly. I'll cherry-pick
them and cherry-pick your patch soon.

Skipped the patch to disable box/on_shutdown.test.lua, because now it is
already fixed with another patch.

WBR, Alexander Turenko.

On Tue, Jun 25, 2019 at 07:57:59PM +0300, Alexander V. Tikhonov wrote:
>     Enable GitLab CI testing
>     
>     Implemented GitLab CI testing process additionally to existing Travis
>     CI. The new testing process is added to run tests faster. It requires to
>     control a load of machines to avoid flaky fails on timeouts. GitLab CI
>     allows us to run testing on our machines.
>     
>     Created 2 stages for testing and deploying packages.
>     
>     The testing stage contains the following jobs that are run for all
>     branches:
>     
>     * Debian 9 (Stretch): release/debug gcc.
>     * Debian 10 (Buster): release clang8 + lto.
>     * OSX 14 (Mojave): release.
>     * FreeBSD 12: release gcc.
>     
>     And the following jobs that are run of long-term branches (release
>     branches: for now it is 1.10, 2.1 and master):
>     
>     * OSX 13 (Sierra): release clang.
>     * OSX 14 (Mojave): release clang + lto.
>     
>     The deployment stage contains the same jobs as we have in Travis CI.
>     They however just build tarballs and packages: don't push them to S3 and
>     packagecloud.
>     
>     The additional manual work is needed when dependencies are changed in
>     .travis.mk file ('deps_debian' or 'deps_buster_clang_8' goals):
>     
>      | make GITLAB_USER=foo -f .gitlab.mk docker_bootstrap
>     
>     This command pushes docker images into GitLab Registry and then they are
>     used in testing. Pre-built images speed up testing.
>     
>     Fixes #4156
> 
> Github: https://github.com/tarantool/tarantool/tree/avtikhon/gh-4156-gitlab-ci-testing
> Issue: https://github.com/tarantool/tarantool/issues/4156
> 
> Alexander V. Tikhonov (2):
>   test: temporary disable on_shutdown.test.lua test
>   Enable GitLab CI testing
> 
>  .gitlab-ci.yml                              | 321 ++++++++++++++++++++
>  .gitlab.mk                                  | 107 +++++++
>  .travis.mk                                  | 107 +++++--
>  .travis.yml                                 |   3 +
>  test/app-tap/console.skipcond               |   7 +
>  test/app-tap/debug.skipcond                 |   8 +
>  test/app-tap/http_client.skipcond           |   7 +
>  test/app-tap/minimal.skipcond               |   8 +
>  test/app-tap/pwd.skipcond                   |   8 +
>  test/app-tap/tarantoolctl.skipcond          |   8 +
>  test/app/crypto.skipcond                    |   7 +
>  test/app/digest.skipcond                    |   7 +
>  test/app/socket.skipcond                    |   5 +
>  test/box-tap/cfg.skipcond                   |   8 +
>  test/box/net.box.skipcond                   |   7 +
>  test/box/net_msg_max.skipcond               |   7 +
>  test/box/suite.ini                          |   2 +-
>  test/replication/misc.skipcond              |   7 +
>  test/replication/skip_conflict_row.skipcond |   7 +
>  test/wal_off/snapshot_stress.skipcond       |   7 +
>  20 files changed, 620 insertions(+), 28 deletions(-)
>  create mode 100644 .gitlab-ci.yml
>  create mode 100644 .gitlab.mk
>  create mode 100644 test/app-tap/console.skipcond
>  create mode 100644 test/app-tap/debug.skipcond
>  create mode 100644 test/app-tap/http_client.skipcond
>  create mode 100644 test/app-tap/minimal.skipcond
>  create mode 100644 test/app-tap/pwd.skipcond
>  create mode 100644 test/app-tap/tarantoolctl.skipcond
>  create mode 100644 test/app/crypto.skipcond
>  create mode 100644 test/app/digest.skipcond
>  create mode 100644 test/box-tap/cfg.skipcond
>  create mode 100644 test/box/net.box.skipcond
>  create mode 100644 test/box/net_msg_max.skipcond
>  create mode 100644 test/replication/misc.skipcond
>  create mode 100644 test/replication/skip_conflict_row.skipcond
>  create mode 100644 test/wal_off/snapshot_stress.skipcond
> 
> -- 
> 2.17.1
> 

      parent reply	other threads:[~2019-07-04 19:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1561481610.git.avtikhon@tarantool.org>
     [not found] ` <15e303a64d13105951fbfa1db4391bef4fcef324.1561481610.git.avtikhon@tarantool.org>
2019-07-04 14:04   ` [tarantool-patches] Re: [PATCH v6 1/2] test: temporary disable on_shutdown.test.lua test Alexander Turenko
2019-07-04 19:47 ` Alexander Turenko [this message]

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=20190704194734.guyyzlcdhrfapei3@tkn_work_nb \
    --to=alexander.turenko@tarantool.org \
    --cc=avtikhon@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH v6 0/2] Enable GitLab CI testing' \
    /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