Am Samstag, den 21.11.2020, 09:46 +0100 schrieb Jonas Hahnfeld: > Am Freitag, den 20.11.2020, 17:55 -0500 schrieb Dan Eble: > > On Nov 20, 2020, at 12:22, Jonas Hahnfeld <[email protected]> wrote: > > > > > Despite these shortcomings, I think it would make sense to enable > > > > > this first implementation in lilypond/lilypond. What do you think? > > > > > > > > > > > > > yes, +1 . I am especially happy that this will likely have no extra > > > > overhead. > > > > > > No extra overhead per pipeline in MRs, but you get an extra pipeline > > > for every merge to master. We'll see if this poses a serious problem… > > > > Given the positive feedback this change has already received, can we > > accelerate its progress? I'm eager to have it in place because I've > > got a branch with new some regression tests ready. > > Sure, I can merge !517 later today and then work on the second MR to > actually enable 'make check' in the pipelines.
Something's not working correctly here: https://hahnjo.gitlab.io/-/lilypond/-/jobs/864846942/artifacts/test-results/index.html The test-baseline was generated by frog (using parallelism), check executed on a shared runner. I thought I had tested using a test- baseline with different number of cores... Probably won't figure this out today since I want to listen to some great film music by Howard Shore - well yes, including the film. Jonas
signature.asc
Description: This is a digitally signed message part
