[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: On elisp running native

From: Andrea Corallo
Subject: Re: On elisp running native
Date: Sat, 07 Mar 2020 18:49:42 +0000
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)

Michael Albinus <address@hidden> writes:

> Andrea Corallo <address@hidden> writes:
>> Hi Michael,
> Hi Andrea,
> [re-adding address@hidden]
>> so apparently it works but as expected we got time out:
>> https://emba.gnu.org/emacs/emacs/-/jobs/5172
> Yes, we have set the project-specific timeout to 90m. We shouldn't
> change it, because the jobs hang sometimes.
>> I think we should raise the project time-out
>> https://emba.gnu.org/help/ci/runners/README.html#setting-maximum-job-timeout-for-a-runner
>> that's apparently the upperbound that can then limited afterwards for
>> each "Runner" (thing I still have to totally understand what it is :)
>> what do you think about?
> I believe the better approach is to set the timeout on job-level for
> your test. See <https://docs.gitlab.com/ce/ci/yaml/README.html#timeout>.

Thanks I can push a commit to do that.

What about adding also -j2 in the make?  Testing the parallel build is
good plus I suspect giving a little more steam to the process would




reply via email to

[Prev in Thread] Current Thread [Next in Thread]