Tarantool development patches archive
 help / color / mirror / Atom feed
From: Alexander Turenko <alexander.turenko@tarantool.org>
To: Alexander Tikhonov <avtikhon@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH v1] travis-ci: fix OSX max files limits
Date: Thu, 25 Jul 2019 00:40:11 +0300	[thread overview]
Message-ID: <20190724214010.zysu3ak7e5p3fe4n@tkn_work_nb> (raw)
In-Reply-To: <1563995566.727319504@f118.i.mail.ru>

> >On Tue, Jul 23, 2019 at 10:51:09AM +0300, Alexander V. Tikhonov wrote:
> >> Increased the maximum number of open file descriptors on macOS:
> >>   Travis-ci needed the "ulimit -n <value>" call
> >>   Gitlab-ci needed the "launchctl limit maxfiles <value>" call
> >> Also gitlib-ci needed the password to change the limits, while
> >> travis-ci run under root user. Limit setup set in the same
> >> call as tests runs call.
> >
> >Are you know what is a reason of the difference between travis-ci and
> >gitlab-ci? I don't insist, but if it is known, it worth to mention it.

> Right, there is the difference that we use different images, travis-ci uses
> its own image, while gitlab-ci we provided the needed image manually.
> Also the travis-ci runs under root user, while gitlab-ci we know the root
> password and can run sudo command with the password. So I've added
> more comments into commit log about it.

I think it is better to implement non-password sudo in our images and
use it in the same way for both testing pipelines. However if it is
complex thing, okay, let it be.

      parent reply	other threads:[~2019-07-24 21:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <34290551efba4c2287e6ffdaea5caf6aea7539b5.1563868186.git.avtikhon@tarantool.org>
2019-07-24  9:37 ` Alexander Turenko
     [not found]   ` <1563995566.727319504@f118.i.mail.ru>
2019-07-24 21:40     ` 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=20190724214010.zysu3ak7e5p3fe4n@tkn_work_nb \
    --to=alexander.turenko@tarantool.org \
    --cc=avtikhon@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH v1] travis-ci: fix OSX max files limits' \
    /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