Re: Emba/Gitlab tests

[Alan Third]

On Thu, Aug 27, 2020 at 08:00:59PM +0200, Michael Albinus wrote:
> Alan Third <alan@idiocy.org> writes:
> 
> Hi ALan,
> 
> > Does this look acceptable? I don't want to have to push a whole bunch
> > of commits to work out any kinks, but I don't know how else to test
> > the code.
> 
> Well, finally you have to do until it works as expected. Create a new
> branch, and test this.

That makes sense.

> > +    - ./autogen.sh autoconf
> > +    - ./configure --without-makeinfo --with-ns
> > +    - make bootstrap
> > +    - make install
> 
> I have no idea what "make install" will do on emba. Do you need it? The
> other test sections don't run it.

On NS builds it packages everything into nextstep/Emacs.app, and
doesn't actually "install" anything. It's probably not necessary, but
I think it makes sense to run it.

Unless this Gitlab instance is set up funny all the jobs should be run
in their own docker containers anyway, so you always get a clean
environment every time. If you want to retain anything between jobs
you have to use the "Artifacts" keyword, and that's only for a single
pipeline anyway, iirc.

> OTOH, if you have a test file specific for gnustep, you could run it by
> 
>     - make -C test gnustep-tests

Unfortunately we don't have any, as far as I'm aware.
-- 
Alan Third