Re: Version 2.21.3

2020-07-16 Thread Jonas Hahnfeld via Discussions on LilyPond development
Hi, Am Donnerstag, den 16.07.2020, 19:01 +0200 schrieb Pierre Perol- Schneider: > Hi, > Test: \version "2.21.3" { c' } > With this last version, the first compilation is OK, but the second is > failing: > > Starting lilypond-windows.exe 2.21.3 [Untitled]... > Processing > `C:/Users/Pierre/AppDa

Re: FontForge errors in CI logs

2020-07-16 Thread Jean Abou Samra
Hello, Le 16/07/2020 à 17:41, James Lowe a écrit : On 16/07/2020 15:46, Jean Abou Samra wrote: Hi, FontForge messages are appearing in the logs of the Build stage in CI pipelines. Have a look at this one: https://gitlab.com/lilypond/lilypond/-/jobs/641609041 ... Should we pay attention to

Re: FontForge errors in CI logs

2020-07-16 Thread James Lowe
On 16/07/2020 15:46, Jean Abou Samra wrote: Hi, FontForge messages are appearing in the logs of the Build stage in CI pipelines. Have a look at this one: https://gitlab.com/lilypond/lilypond/-/jobs/641609041 ... |Should we pay attention to that? It was diagnosed as a 'problem' in font for

FontForge errors in CI logs

2020-07-16 Thread Jean Abou Samra
Hi, FontForge messages are appearing in the logs of the Build stage in CI pipelines. Have a look at this one: https://gitlab.com/lilypond/lilypond/-/jobs/641609041 Internal Error (overlap) in noteheads.uM3neomensural: Mismatched intersection. | (669.462,430.017)->(650.002,178.75) ends at (-

Re: Today's problem with GUB build

2020-07-16 Thread David Kastrup
Han-Wen Nienhuys writes: > On Wed, Jul 15, 2020 at 10:48 PM David Kastrup wrote: > >> Well ok. But only 100 random numbers are being used (there is >> another call using 1000 instead, the choice appearing random). >> Let's assume we have 10 processes going through 138 files each. The >

Re: Today's problem with GUB build

2020-07-16 Thread Han-Wen Nienhuys
On Wed, Jul 15, 2020 at 10:48 PM David Kastrup wrote: > Well ok. But only 100 random numbers are being used (there is > another call using 1000 instead, the choice appearing random). > Let's assume we have 10 processes going through 138 files each. The > processes are going to switch to

Re: Today's problem with GUB build

2020-07-16 Thread Jean Abou Samra
Le 15/07/2020 à 22:48, David Kastrup a écrit : Now if I remember correctly, there were some changes in how lilypond-book worked that typically resulted in double the number of processes getting spawned than asked for which would give us 19 instead of 9 possibilities for collision. That would ra

PATCHES - Countdown for July 16th

2020-07-16 Thread James
Hello, Here is the current patch countdown list. The next countdown will be on July 18th. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !240 Music_iterator: get_own_context and set_own_context - Dan Eble

Re: Today's problem with GUB build

2020-07-16 Thread Jean Abou Samra
Hi David, Le 15/07/2020 à 23:01, David Kastrup a écrit : Not using random at all but using the pid, in contrast, should be collision-proof, assuming that we are not working on a shared file system accessed by multiple computers with separate process id pools. But then locking is likely to be non