emacs-build-automation
[Top][All Lists]
Advanced

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

Re: emba.gnu.org overload


From: Andrea Corallo
Subject: Re: emba.gnu.org overload
Date: Tue, 06 Dec 2022 13:43:39 +0000
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux)

Mattias Engdegård <mattiase@acm.org> writes:

> 5 dec. 2022 kl. 17.17 skrev Michael Albinus <michael.albinus@gmx.de>:
>
>> For example, four different jobs for native-compilation builds are run,
>> build-native-comp-speed{0,1,2} and test-native-comp-speed0. That was
>> fine for development of this feature, but perhaps not so important these
>> days. We might ask Andrea Corallo about.
>> 
>> Also the platform tests build-image-{filenotify-gio,gnustep} and
>> test-{filenotify-gio,gnustep} could be reduced. We don't need them in
>> both emacs-29 and master pipelines; for the time being we might disable
>> them in master.
>
> Then let's drop all of these and see how far that takes us.
> Once enough load has been shed for everything to run in a sustainable way we 
> can think about reinstating some of it.

Hi all,

I believe the right fix, instead of dropping configurations, would be to
have a decent machine to run on.  Can't we ask for more resources?  ATM
these are extremely limited to the point where even building few Emacs
instances is a problem.  Now days bootstrap time has been greatly reduced
even compared to when we added these builds to emba, I'm surprised to
see we cannot afford it.

My main worry (almost a certainty) is that once these configurations are
removed from the test-bed they will never be added again in the future
following the well known rule of: "Nothing is more permanent than a
temporary solution".

Best Regards

  Andrea



reply via email to

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