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

[Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org>]

On 14.10.26, Alexander Turenko wrote:
> > > 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
> 
> I agree that it is good to have job timeouts.
> 
> I’d let the maintainers to set appropriate timeouts.
> Personally, I neither use the jobs nor know details about them.
> And I don’t think that it becomes more urgent when we switch
> from 6 parallel runners to 60 (I’d say the opposite).
> 
> WBR, Alexander Turenko

OK, lets do it in the separate patch.

-- 
Best regards,
Sergey Kaplun