Skip to content
Snippets Groups Projects
Unverified Commit 5fa2d0aa authored by Yaroslav Lobankov's avatar Yaroslav Lobankov
Browse files

ci: update matrix strategy for osx testing

It has been decided to have only release and debug builds for testing
on two latest macOS versions (at this momemnt, 13 and 14). Static and
LTO builds are dropped.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

(cherry picked from commit 47940311)
parent 63af960f
No related branches found
No related tags found
No related merge requests found
......@@ -17,34 +17,14 @@ jobs:
strategy:
fail-fast: false
matrix:
osx-version: [ 14 ]
osx-version: [ 13, 14 ]
machine-arch: [ x86_64, aarch64 ]
tarantool-branch:
- 'master'
- 'release/3.0'
- 'release/2.11'
- 'release/2.10'
build-type: [ debug, release, release-lto, static-cmake ]
include:
- osx-version: 13
machine-arch: x86_64
tarantool-branch: 'master'
build-type: release
- osx-version: 13
machine-arch: x86_64
tarantool-branch: 'release/3.0'
build-type: release
- osx-version: 13
machine-arch: x86_64
tarantool-branch: 'release/2.11'
build-type: release
- osx-version: 13
machine-arch: x86_64
tarantool-branch: 'release/2.10'
build-type: release
env:
BUILD_TYPE: ${{ matrix.build-type }}
build-type: [ debug, release ]
steps:
- name: Prepare checkout
......@@ -62,14 +42,8 @@ jobs:
- name: Install deps
uses: ./.github/actions/install-deps-osx
- name: Enable LTO for build
if: endsWith(matrix.build-type, '-lto')
run: |
echo "BUILD_TYPE=${BUILD_TYPE/-lto/}" >> $GITHUB_ENV
echo "CMAKE_EXTRA_PARAMS=-DENABLE_LTO=ON" >> $GITHUB_ENV
- name: Run testing
run: make -f .test.mk test-osx-${{ env.BUILD_TYPE }}
run: make -f .test.mk test-osx-${{ matrix.build-type }}
- name: Send VK Teams message on failure
if: failure()
......@@ -117,7 +91,7 @@ jobs:
#
# For some reason, sometimes GitHub doesn't give the complete job list
# and there is no chance to find the job and get its ID. At least, it
# has been noticed for this workflow with 36 parallel jobs.
# has been noticed for this workflow with 32 parallel jobs.
#
# It looks like the issue resides on the GitHub side and the simplest
# way to resolve this is to ignore the failure and not fail the whole
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment