Am Samstag, den 26.10.2019, 08:43 +0100 schrieb James: > 1. ./autogen --noconfigure > > 2. mkdir build > > 3. cd build > > 4 ../configure --disable-optimising > > 5. make -j7 CPU_COUNT=7 > > 6. make -j7 CPU_COUNT=7 test-baseline > > 7. make -j7 CPU_COUNT=7 check > > 8. > > ... > > no source for input/regression/midi/out-test/dynamic-initial-1.midi > no source for input/regression/midi/out-test/tree.gittxt > no source for input/regression/midi/out-test/sequence-name-2.midi > output-distance summary: > 3 changed > 467 below threshold > 3562 unchanged > writing > /home/james/lilypond-git/build/out/test-results/input/regression/out-test-baseline/test-output-distance.png > writing > /home/james/lilypond-git/build/out/test-results/input/regression/out-test/test-output-distance.png > convert-im6.q16: profile 'icc': 'RGB ': RGB color space not permitted on > grayscale PNG `/tmp/tmplG8Fok/crop1.png' @ > warning/png.c/MagickPNGWarningHandler/1654. > convert-im6.q16: profile 'icc': 'RGB ': RGB color space not permitted on > grayscale PNG `/tmp/tmplG8Fok/crop2.png' @ > warning/png.c/MagickPNGWarningHandler/1654. > writing > /home/james/lilypond-git/build/out/test-results/input/regression/out-test-baseline/rest-dot-position.png > writing > /home/james/lilypond-git/build/out/test-results/input/regression/out-test/rest-dot-position.png > convert-im6.q16: profile 'icc': 'RGB ': RGB color space not permitted on > grayscale PNG `/tmp/tmplG8Fok/crop1.png' @ > warning/png.c/MagickPNGWarningHandler/1654. > convert-im6.q16: profile 'icc': 'RGB ': RGB color space not permitted on > grayscale PNG `/tmp/tmplG8Fok/crop2.png' @ > warning/png.c/MagickPNGWarningHandler/1654. > writing /home/james/lilypond-git/build/out/test-results/index.txt > Validating > /home/james/lilypond-git/build/out/test-results/input/regression/out-test/rest-dot-position.details.html > /bin/sh: 3: -: not found > /home/james/lilypond-git/GNUmakefile.in:370: recipe for target > 'local-check' failed > make: *** [local-check] Error 1 > > ... > > > Note that I didn't apply any patches (it also breaks when you apply > patches - in case you didn't get that). > > It seems that patch testing is getting more and more unreliable and time > consuming for me these last few months - I am the only one that bothers > to do it in case you didn't get that either. Testing from a supposed > clean master is throwing up stuff that never was detected when patches > were tested before being committed. > > I am not a developer, I just run a bunch-of-commands, in sequence, line > by command line, that I have always run (for like 8+ years). > > I use a vanilla Linux install from a very standard and popular > distribution (before someone asks me for the umpteenth time what I have > installed and tells me that it works for them). > > I am not going to even bother debugging this - as if I even could. > > No patch testing today folks! (currently 4 in the queue at the moment). > > I'll check back tomorrow and see if anything has changed.
I already debugged this, and assuming you don't have tidy installed (I don't have either), please apply https://sourceforge.net/p/testlilyissues/issues/5586/ first. Regards, Jonas P.S.: I'll update the patch in a second to incorporate Dan's feedback.
signature.asc
Description: This is a digitally signed message part