[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: failing CI builds

From: Jonas Hahnfeld
Subject: Re: failing CI builds
Date: Sun, 28 Jun 2020 14:33:04 +0200
User-agent: Evolution 3.36.3

Am Samstag, den 27.06.2020, 18:25 +0200 schrieb Han-Wen Nienhuys:
> On Fri, Jun 26, 2020 at 11:37 PM Jonas Hahnfeld <> wrote:
> >
> Curious, this change can't affect lilypond execution. Are the failures
> localized to certain runners?

No, I can reproduce this locally with current master when running plain
"make doc" without parallelism. It started after

commit 99ee305b37d5804cd215cd8a222ec8a1eccb8caf
Author: Han-Wen Nienhuys <>
Date:   Wed Jun 17 23:12:27 2020 +0200

    Write output files atomically

or more precisely after the command to flush PDF output. However, the
other MR triggered a similar problem before this commit landed in
master, so I would tend to say that it just triggers an existing

> > 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 - any ideas?
> Can you install debug symbols for GUILE? It would be interesting to
> see a more precise stacktrace.

Did this yesterday (before I had to leave), find it attached.


Attachment: backtrace.dbg.txt
Description: Text document

Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]