Re: testing out Docker CI scripts?

[Jan Nieuwenhuizen]

Han-Wen Nienhuys writes:

> -james
>
> On Sun, Feb 23, 2020 at 1:42 PM Han-Wen Nienhuys <address@hidden> wrote:
>>
>> On Sun, Feb 23, 2020 at 1:17 PM Jan Nieuwenhuizen <address@hidden> wrote:
>> > > Please pull and try again
>> > >
>> > >> test-git.sh: line 78: local_repo: unbound variable
>> > >
>> > > yeah, who tests the testers? :-)
>> >
>> > If I'm a tester, then I think that could be you ... :-)
>> >
>> > > (I don't test the whole setup start to front because creating the base
>> > > images is very slow.)
>> >
>> > Much better!  I have reconfigured my system to include a docker service.
>> > Now the problem may be X or Y.
>>
>> cool. Fixed; please pull.

I found that reseed.sh fails early when lilypond is a work tree (log
attached).  After doing

--8<---------------cut here---------------start------------->8---
(cd lilypond; git worktree move ../lilypond ../lilypond-worktree)
git clone gnu:lilypond lilypond
--8<---------------cut here---------------end--------------->8---

to use a full clone it only failed after ~half an hour (full log
attached) like so

--8<---------------cut here---------------start------------->8---
configure: creating ./config.status
config.status: creating config.make
config.status: creating config.hh

WARNING: Please consider installing optional programs or files:  guile

ERROR: Please install required programs:  guile-config2.2 < 1.9.0 (installed: 
2.2.6) (guile-devel, guile-dev or libguile-dev package) libguile (libguile-dev, 
guile-devel or guile-dev package).

See INSTALL.txt for more information on how to build LilyPond
The command '/bin/sh -c ./autogen.sh && make -j$(nproc)   && make test-baseline 
-j$(nproc) CPU_COUNT=$(nproc)   && make distclean   && ccache -z' returned a 
non-zero code: 1
[1]15:17:06 janneke@dundal:~/src/lilypond/lilypond-ci [env]
--8<---------------cut here---------------end--------------->8---

>> >   (I'm a total docker
>> > n00b; when I learned that it needs a daemon to run, I lost interest at
>> > the time).
>>
>> docker is confusing and, in part poorly engineered, but it does
>> provide useful functionality for a number of things.

At the time my target was "run everywhere binaries"; now I won't mind
to learn a few things about what people like about it and where it can
be useful.

>> Docker has a daemon, because it is usually used for managing other
>> daemons, and you need a manager for restarting, allocating network
>> ports, etc.

Ah...are we using any of those?

Greetings,
janneke

reseed.sh-with-workree.log
Description: Binary data

reseed.sh-with-full-clone.log.gz
Description: Binary data

-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com