Re: failing CI builds

[Han-Wen Nienhuys]

On Fri, Jun 26, 2020 at 11:37 PM Jonas Hahnfeld <hahnjo@hahnjo.de> wrote:
>
> Hi all,
>
> at least the following two MRs experience strange failures in CI:
> https://gitlab.com/lilypond/lilypond/-/merge_requests/191
> https://gitlab.com/lilypond/lilypond/-/merge_requests/201
>
> The latter one is mine and I can reproduce this on my own runner, which
> means I can get the log files easily and even connect from the host
> with gdb and get a bracktrace (see attached files). It's failing
> somewhere deep inside libguile.so - any ideas?
>
> When comparing the build artifacts, I noticed that the output files in
> mf/ are not reproducible. I'm not sure if that is related,

Unlikely. For unknown reasons metapost is dumping the current time in
its log output

$  diff -u feta-alphabet11.log ../out1/feta-alphabet11.log
--- feta-alphabet11.log 2020-06-27 18:26:12.545156223 +0200
+++ ../out1/feta-alphabet11.log 2020-06-27 18:25:46.899267077 +0200
@@ -1,4 +1,4 @@
-This is MetaPost, version 2.00 (TeX Live 2019) (kpathsea version
6.3.1)  27 JUN 2020 18:26
+This is MetaPost, version 2.00 (TeX Live 2019) (kpathsea version
6.3.1)  27 JUN 2020 18:25
 **\mode:=localfont; mag:=89.4607843137255; bpppix 0.02; nonstopmode;
input /home/hanwen/vc/lilypond/mf/feta-alphabet11.mf
 (/home/hanwen/vc/lilypond/mf/mf2pt1.mp
(/usr/share/texlive/texmf-dist/metapost/base/mfplain.mp
 Preloading the plain base, version 0.99: preliminaries,


> but the
> lilypond binary itself is reproducible and the container image is for
> sure, so it has to be something else.
>
> Jonas



-- 
Han-Wen Nienhuys - hanwenn@gmail.com - http://www.xs4all.nl/~hanwen