[Tarantool-patches] [PATCH 2/2] ci: run ARM64 jobs on GitHub-hosted runners

[Sergey Kaplun]

Hi, Alexander!
Thanks for the patch!
LGTM, after resolving Sergey's comment below.

On 02.10.26, Sergey Bronnikov wrote:
> Hi, Alexander,
> 
> thanks for the patch! LGTM with minor comment
> 
> Sergey
> 
> On 10/1/26 04:06, Alexander Turenko wrote:
> > The main idea behind the switch is to have less of our own
> > infrastructure to support, see tarantool/tarantool#13278 for details.
> >
> > Drafted by an LLM, conducted and corrected by the commit author.
> > ---
> >   .github/workflows/debuggers.yml              | 3 ++-
> >   .github/workflows/exotic-builds-testing.yml  | 3 ++-
> >   .github/workflows/gnumake-builds-testing.yml | 5 ++++-
> >   .github/workflows/testing.yml                | 5 ++++-
> >   4 files changed, 12 insertions(+), 4 deletions(-)
> >
> > diff --git a/.github/workflows/debuggers.yml b/.github/workflows/debuggers.yml
> > index 489c2bed..d8b53fda 100644
> > --- a/.github/workflows/debuggers.yml
> > +++ b/.github/workflows/debuggers.yml
> > @@ -36,7 +36,8 @@ jobs:
> >           exclude:
> >             - ARCH: ARM64
> >               GC64: OFF
> > -    runs-on: [self-hosted, regular, Linux, '${{ matrix.ARCH }}']
> > +    runs-on: ${{ matrix.ARCH == 'ARM64' && 'ubuntu-26.04-arm' ||
> > +                 fromJSON('["self-hosted", "regular", "Linux", "x86_64"]') }}
> 
> after the patch we will use github runners and it is worth set a timeout 
> for jobs,
> 
> otherwise we might run out of time on the runners (AFAIK it is limited 
> there).

Agree here. IINM, the default is 6 hours [1], which is too much for our
tests.
The longest job is Valgrind job, which is running about 12 minutes.
I suppose the limit of 30 minutes is reasonable.

<snipped>

[1]: https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#jobsjob_idtimeout-minutes

-- 
Best regards,
Sergey Kaplun