Tarantool development patches archive
 help / color / mirror / Atom feed
From: "Alexander Tikhonov" <avtikhon@tarantool.org>
To: "Oleg Piskunov" <o.piskunov@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v1 2/2] gitlab-ci: add Catalina OSX 10.15
Date: Mon, 13 Apr 2020 14:00:16 +0300	[thread overview]
Message-ID: <1586775616.74521266@f247.i.mail.ru> (raw)
In-Reply-To: <1586775047.901364389@f317.i.mail.ru>

[-- Attachment #1: Type: text/plain, Size: 2081 bytes --]


Hi Oleg, thanks for the review, as I see the only question why we may need this patch as a temporary solution. The purpose of this patch is to save the stability of the testing code on OSX version, while this is the only way to test it. It can be used in the standalone branch as it is, without pushing to mainline.

  
>Понедельник, 13 апреля 2020, 13:50 +03:00 от Oleg Piskunov <o.piskunov@tarantool.org>:
> 
>Hi,
> 
>Sasha, thanks for the patch. See my comment below.
>  
>>Четверг, 9 апреля 2020, 11:41 +03:00 от Alexander V. Tikhonov < avtikhon@tarantool.org >:
>> 
>>Added Catalina OSX 10.15 to gitlab-ci testing and removed OSX 10.13,
>>due to decided to have only 2 last major releases, for now it is
>>10.14 and 10.15 OSX versions. Also changed the commit job for branches
>>from 10.14 to 10.15 OSX version.
>As far as I remember we agreed to use new HW mac mini for testing 10.15 OSX version.
>I don’t understand why you trying to use VMS for it.
>>
>>Added to OSX 10.15 additional call to /etc/profile to setup the PATH,
>>otherwise it doesn't have the path to brew installed packages.
>>---
>> .gitlab-ci.yml | 11 ++++++-----
>> 1 file changed, 6 insertions(+), 5 deletions(-)
>>
>>diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
>>index cd710027f..5c9f353a7 100644
>>--- a/.gitlab-ci.yml
>>+++ b/.gitlab-ci.yml
>>@@ -139,19 +139,20 @@ release_asan_clang8:
>>   script:
>>     - ${GITLAB_MAKE} test_asan_debian_no_deps
>> 
>>-osx_13_release:
>>- <<: *release_only_definition
>>+osx_15_release:
>>   <<: *vbox_definition
>>   tags:
>>- - vms_osx_13
>>+ - vms_osx_15
>>   variables:
>>- VMS_NAME: 'osx_13'
>>+ EXTRA_ENV: '. /etc/profile ;'
>>+ VMS_NAME: 'osx_15'
>>     VMS_USER: 'tarantool'
>>- VMS_PORT: '2212'
>>+ VMS_PORT: '2242'
>>   script:
>>     - ${GITLAB_MAKE} vms_test_osx
>> 
>> osx_14_release:
>>+ <<: *release_only_definition
>>   <<: *docker_test_definition
>>   tags:
>>     - osx_14
>>--
>>2.17.1
>>  
> 
> 
>--
>Oleg Piskunov
>  
 
 
--
Alexander Tikhonov
 

[-- Attachment #2: Type: text/html, Size: 3637 bytes --]

  reply	other threads:[~2020-04-13 11:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09  8:40 [Tarantool-patches] [PATCH v1 0/2] " Alexander V. Tikhonov
2020-04-09  8:40 ` [Tarantool-patches] [PATCH v1 1/2] build: disable at OSX curl SSL Alexander V. Tikhonov
2020-04-13 10:57   ` Oleg Piskunov
2020-04-13 14:48     ` Alexander Tikhonov
2020-04-09  8:40 ` [Tarantool-patches] [PATCH v1 2/2] gitlab-ci: add Catalina OSX 10.15 Alexander V. Tikhonov
2020-04-13 10:50   ` Oleg Piskunov
2020-04-13 11:00     ` Alexander Tikhonov [this message]
2020-04-10 14:34 ` [Tarantool-patches] [PATCH v1 0/2] " Sergey Bronnikov
2020-04-13 13:49   ` Alexander Tikhonov

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=1586775616.74521266@f247.i.mail.ru \
    --to=avtikhon@tarantool.org \
    --cc=o.piskunov@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v1 2/2] gitlab-ci: add Catalina OSX 10.15' \
    /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