On Thu, Jun 18, 2020 at 10:18 AM Jonas Hahnfeld wrote:
> > > > 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 test
On Jun 18, 2020, at 03:05, Jonas Hahnfeld wrote:
>
> Am Mittwoch, den 17.06.2020, 18:11 -0400 schrieb Dan Eble:
>> On Jun 14, 2020, at 07:04, Han-Wen Nienhuys wrote:
>>> Hey Dan,
>>>
>>> does your CI runner have limitations on sending data back to Gitlab by any
>>> chance? It looks like this h
Am Donnerstag, den 18.06.2020, 10:47 +0100 schrieb James:
> On 18/06/2020 09:18, Jonas Hahnfeld via Discussions on LilyPond
> development wrote:
>
> > > Another things to consider (if you build docs locally) if to remove
> > > extractpdfmark. It is extremely slow.
> > Ack.
>
> Yes but let's not
On 18/06/2020 09:18, Jonas Hahnfeld via Discussions on LilyPond
development wrote:
Another things to consider (if you build docs locally) if to remove
extractpdfmark. It is extremely slow.
Ack.
Yes but let's not do that for the PDFs we eventually use for the
website. The size savings are wo
Am Donnerstag, den 18.06.2020, 09:57 +0200 schrieb Han-Wen Nienhuys:
> On Thu, Jun 18, 2020 at 9:05 AM Jonas Hahnfeld wrote:
> > > 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?
>
> It's not nec
On Thu, Jun 18, 2020 at 9:05 AM Jonas Hahnfeld wrote:
> > 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?
It's not necessary. I recreated the failing build locally.
The only difference I could fin
uploading the failure logs
> >
> > -- Forwarded message -
> > From: GitLab 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
>
From: GitLab 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
to: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
> To:
>
>
>
> Your pipeline has failed.
>
> Project LilyPond <https://
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
Date: Sun, Jun 14, 2020 at 12:49 PM
Subject: LilyPond | Pipeline #156017999 has failed for dev
10 matches
Mail list logo