[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
failing CI builds
From: |
Jonas Hahnfeld |
Subject: |
failing CI builds |
Date: |
Fri, 26 Jun 2020 23:36:56 +0200 |
User-agent: |
Evolution 3.36.3 |
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, but the
lilypond binary itself is reproducible and the container image is for
sure, so it has to be something else.
Jonas
snippet-names-03bf0ea10d1ef3b2ae481a128b891ce1.log
Description: Text Data
backtrace.txt
Description: Text document
signature.asc
Description: This is a digitally signed message part
- failing CI builds,
Jonas Hahnfeld <=
Re: failing CI builds, Han-Wen Nienhuys, 2020/06/27