Re: On elisp running native

[Andrea Corallo]

Michael Albinus <address@hidden> writes:

> I don't know whether you are familiar with gitlab's CI. In case you are,
> and you want to use it: Emacs runs an own gitlab instance on
> <https://emba.gnu.org>. You'll see there that your last commit has
> failed the CI test, see <https://emba.gnu.org/emacs/emacs/-/jobs/5147/raw>.

Hi Michael,

thanks for the info, these prove to be already very useful! :)

I didn't know the CI was running all branches.  As I'm rarely building
the non native configuration on that branch (unless when doing
comparisons) I'll certanly keep a look on it since today.

Should be fixed by now lets see if it pass then.

> Besides fixing this, you could also *add* own CI tests, which will be
> run once your branch has seen any git push. The tests are described in
> Emacs' root directory, file .gitlab-ci.yml. Read also admin/notes/emba.
>
> Just in case you're interested in.

I'd be certanly very interested.  The issue could be that, as of today,
bootstrapping and native compiling the whole Emacs is about 7h total cpu
time (to be divided by the machine parallelism).  Not sure how many cpu
threads emba.gnu.org has and if we want to load it with this.

Regards

  Andrea

--
address@hidden