From: Sergey Kaplun <skaplun@tarantool.org>
To: Evgeniy Temirgaleev <e.temirgaleev@tarantool.org>
Cc: Sergey Bronnikov <sergeyb@tarantool.org>,tarantool-patches@dev.tarantool.org
Date: Wednesday, August 19, 2026 10:31 AM +03:00
 

Hi, Evgeniy!
Thanks for the answers!
LGTM, with minor suggestion below.

On 18.08.26, Evgeniy Temirgaleev wrote:
> Hi, Sergey! Thanks for review!
>
> >
> > From: Sergey Kaplun <skaplun@tarantool.org>

<snipped>

> > b/.github/actions/setup-sanitizers-linux/action.yml
> > > similarity index 76%
> > > rename from .github/actions/setup-sanitizers/action.yml
> > > rename to .github/actions/setup-sanitizers-linux/action.yml
> > > index 8642d553..18f5a75d 100644
> > > --- a/.github/actions/setup-sanitizers/action.yml
> > > +++ b/.github/actions/setup-sanitizers-linux/action.yml
> > > @@ -20,13 +20,17 @@ runs:
> > > - name: Install build and test dependencies
> > > run: |
> > > apt -y update
> > > + echo Available compilers:
> > > + export CC_FAMILY=`echo ${CC_NAME} | sed 's/-.*$//'`
> > > + apt list | grep -Pe "^${CC_FAMILY}-[0-9]+/"
> > > + # Try to install
> > > apt -y install ${CC_NAME} libstdc++-10-dev cmake ninja-build make perl
> > > shell: bash
> > > env:
> > > CC_NAME: ${{ inputs.cc_name }}
> > > - - name: Set specific C compiler as a default toolchain
> > > + - name: Set specific C compiler as a default toolchain for cmake
> > > run: |
> > > - echo CC=${CC_NAME} | tee -a $GITHUB_ENV
> > > + echo CMAKE_C_COMPILER=${CC_NAME} | tee -a $GITHUB_ENV
> > > shell: bash
> > > env:
> > > CC_NAME: ${{ inputs.cc_name }}
> >
> > These changes look like debugging of the workflow. Are they necessary?
> >
>
> I think it’s a useful information: Which compiler we can select just now with the current runner? For example, it used to answer your question below.
> I added it advisedly, as it done for macOS action.

Got it. Please add the comment and the note about it in the commit
message to avoid confusion.

>
> >
> >
> > > diff --git a/.github/actions/setup-sanitizers-macos/README.md
> > b/.github/actions/setup-sanitizers-macos/README.md
> > > new file mode 100644
> > > index 00000000..9ac5eb38
> > > --- /dev/null
> > > +++ b/.github/actions/setup-sanitizers-macos/README.md
> >
> > <snipped>
> >
> > > diff --git a/.github/actions/setup-sanitizers-macos/action.yml
> > b/.github/actions/setup-sanitizers-macos/action.yml
> > > new file mode 100644
> > > index 00000000..9836ea03
> > > --- /dev/null
> > > +++ b/.github/actions/setup-sanitizers-macos/action.yml
> > > @@ -0,0 +1,73 @@
> >
> > <snipped>
> >
> > > + - name: Set CMAKE_BUILD_PARALLEL_LEVEL
> > > + shell: bash
> > > + run: |
> > > + # Set CMAKE_BUILD_PARALLEL_LEVEL environment variable to
> > > + # limit the number of parallel jobs for build/test step.
> > > + NPROC=$(sysctl -n hw.logicalcpu 2>/dev/null)
> > > + echo CMAKE_BUILD_PARALLEL_LEVEL=$(($NPROC + 1)) | tee -a $GITHUB_ENV
> > > + - name: Set MACOSX_DEPLOYMENT_TARGERT
> > > + shell: bash
> > > + run: |
> > > + # Set required MACOSX_DEPLOYMENT_TARGERT environment
> > > + # variable for Makefile.original build.
> > > + # See https://github.com/LuaJIT/LuaJIT/issues/484,
> > > + # https://github.com/LuaJIT/LuaJIT/issues/653.
> > > + echo MACOSX_DEPLOYMENT_TARGET=$(sw_vers -productVersion) | tee -a
> > $GITHUB_ENV
> > > + - name: Install build and test dependencies
> > > + shell: bash
> > > + run: |
> > > + # Install brew using the command from Homebrew repository
> > > + # instructions: https://github.com/Homebrew/install.
> > > + # XXX: 'echo' command below is required since brew
> > > + # installation script obliges the one to enter a newline
> > > + # for confirming the installation via Ruby script.
> > > + brew update ||
> > > + echo | /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install
> > )"
> > > + # Try to install the packages either upgrade it to avoid
> > > + # of fails if the package already exists with the previous
> > > + # version.
> > > + brew install --force ${CC_FORMULA} cmake make ninja perl ||
> > > + brew upgrade ${CC_FORMULA} cmake make ninja perl
> >
> > Can we reuse setup-macos action instead these 3 steps?
> >
>
> Yes, we can do it on top of the «ci: unused gcc removed from macOS setup» patch.
> So, we need to merge it first.

Do we? Don't understand why it is required. The gcc instalation and
upgrade looks harmless, IINM.

>  And then I shall update this patch.
> Thanks for the notice.
>
> >
> >

--
Best regards,
Sergey Kaplun