Re: failing CI builds

[Jonas Hahnfeld]

Am Sonntag, den 28.06.2020, 14:33 +0200 schrieb Jonas Hahnfeld:
> Am Samstag, den 27.06.2020, 18:25 +0200 schrieb Han-Wen Nienhuys:
> > 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?
> 
> No, I can reproduce this locally with current master when running plain
> "make doc" without parallelism.

For another proof, see the following job on the shared runners:
https://gitlab.com/lilypond/lilypond/-/jobs/614267358

> It started after
> 
> commit 99ee305b37d5804cd215cd8a222ec8a1eccb8caf
> Author: Han-Wen Nienhuys <hanwenn@gmail.com>
> 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
> problem.

Even if just triggering the problem, we might need to revert at least
the part that provides atomic output with the GS API. Right now, I
think we can only merge if the pipeline after rebase happens to execute
on a runner with enough parallelism. Which is really unfortunate.

Jonas

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