[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: failing CI builds
From: |
Han-Wen Nienhuys |
Subject: |
Re: failing CI builds |
Date: |
Sat, 27 Jun 2020 18:25:33 +0200 |
On Fri, Jun 26, 2020 at 11:37 PM Jonas Hahnfeld <hahnjo@hahnjo.de> wrote:
> https://gitlab.com/lilypond/lilypond/-/merge_requests/201
Curious, this change can't affect lilypond execution. Are the failures
localized to certain runners?
> 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?
Can you install debug symbols for GUILE? It would be interesting to
see a more precise stacktrace.
> When comparing the build artifacts, I noticed that the output files in
> mf/ are not reproducible. I'm not sure if that is related, but the
> lilypond binary itself is reproducible and the container image is for
> sure, so it has to be something else.
--
Han-Wen Nienhuys - hanwenn@gmail.com - http://www.xs4all.nl/~hanwen
Re: failing CI builds, Han-Wen Nienhuys, 2020/06/27