Am Mittwoch, den 17.06.2020, 18:11 -0400 schrieb Dan Eble: > On Jun 14, 2020, at 07:04, Han-Wen Nienhuys <hanw...@gmail.com> wrote: > > Hey Dan, > > > > does your CI runner have limitations on sending data back to Gitlab by any > > chance? It looks like this hung while uploading the failure logs > > > > ---------- Forwarded message --------- > > From: GitLab <git...@mg.gitlab.com <mailto:git...@mg.gitlab.com>> > > Date: Sun, Jun 14, 2020 at 12:49 PM > > Subject: LilyPond | Pipeline #156017999 has failed for dev/hanwen/doc-build > > | 47b263b1 in !84 > > Would you like me to take my runner offline for a bit and trigger a rebuild > of this pipeline to see whether it will succeed on another runner?
Did anyone try to build the changes of the MR locally? Early versions of the description said that it's known to break the build, so I wouldn't blame the runner for now. > It would be nice to advance this MR since it seems to take about 25% off the > time required for the doc stage (on my runner). Where do you get that 25% from, with no version of the MR passing automated CI testing? Sure, the jobs currently finish earlier than other doc builds - simply because they fail along the way. As far as I can tell, the failing builds haven't produced any PDF for the NR yet which is (IIRC) the largest single documentation that we have. Jonas
signature.asc
Description: This is a digitally signed message part
