grenoui...@lilynet.net writes: > 21:58:01 (UTC) Begin LilyPond compile, previous commit at > e15e0d22810063b79da891bbf472ecc39d09c02c > 21:58:15 From git.savannah.gnu.org:/srv/git/lilypond > 5d2bd06..e15e0d2 master -> master > 201be86..e593c62 translation -> translation > 21:58:59 Merged staging, now at: e15e0d22810063b79da891bbf472ecc39d09c02c > 21:59:01 Success: sudo -u lilybuild ./autogen.sh > --noconfigure > 21:59:37 Success: sudo -u lilybuild > /home/lilybuild/staging/configure --disable-optimising > 21:59:47 Success: sudo -u lilybuild nice make clean > 22:00:30 *** FAILED BUILD *** > sudo -u lilybuild nice make -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1 > Previous good commit: 66a7c3e925cbc1a34eaad04f80d4bc42ad9834ac > Current broken commit: e15e0d22810063b79da891bbf472ecc39d09c02c > 22:00:30 *** FAILED STEP *** > merge from staging > Failed runner: sudo -u lilybuild nice make -j2 CPU_COUNT=2 > ANTI_ALIAS_FACTOR=1 > See the log file log-staging-nice-make--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt > 22:00:31 Traceback (most recent call last): > File > "/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init_
[...] Grenouille currently seems to be wrong too often to be useful. Do you have a way of checking the integrity of its RAM? -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
