Hello, On 17/11/15 15:46, pat...@gnu.org wrote: > 15:37:38 (UTC) Begin LilyPond compile, previous commit at > 84ac019c437ea40b7b18ab46da1772f6db344a83 > 15:37:42 Merged staging, now at: 84ac019c437ea40b7b18ab46da1772f6db344a83 > 15:37:43 Success: ./autogen.sh --noconfigure > 15:38:01 Success: /tmp/lilypond-autobuild/configure > --enable-checking > 15:38:05 Success: nice make clean > 15:46:06 *** FAILED BUILD *** > nice make -j3 CPU_COUNT=3 > Previous good commit: 95b22392ab6ee4bdfd23906eb796e907185a1c20 > Current broken commit: 84ac019c437ea40b7b18ab46da1772f6db344a83 > 15:46:06 *** FAILED STEP *** > merge from staging > Failed runner: nice make -j3 CPU_COUNT=3 > See the log file log-staging-nice-make--j3-CPU_COUNT=3.txt > 15:46:06 Traceback (most recent call last): > File > "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", > line 528, in handle_staging > self.build (issue_id=issue_id) > File > "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", > line 316, in build > issue_id) > File > "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", > line 266, in runner > raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, > this_logfilename)) > FailedCommand: Failed runner: nice make -j3 CPU_COUNT=3 > See the log file log-staging-nice-make--j3-CPU_COUNT=3.txt > > _______________________________________________ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel > > I saw you were running this so ran my own patchy, and it pushed OK.
Hopefully yours is OK too? Thanks for fixing it, I didn't catch what the problem was. James _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel