pat...@gnu.org writes: > 09:24:04 (UTC) Begin LilyPond compile, previous commit at > 309687117b7a10b20cd958147174a906e308ccb6 > 09:24:16 Merged staging, now at: 309687117b7a10b20cd958147174a906e308ccb6 > 09:24:18 Success: ./autogen.sh --noconfigure > 09:24:43 Success: /tmp/lilypond-autobuild/configure > --disable-optimising > 09:24:48 Success: nice make clean > 09:30:08 Success: nice make -j3 > 09:39:37 Success: nice make test -j3 > 09:54:56 *** FAILED BUILD *** > nice make doc -j3 > Previous good commit: 188c8e6d80df96e4ef7040e0df5b7b1520260d36 > Current broken commit: 309687117b7a10b20cd958147174a906e308ccb6 > 09:54:56 *** FAILED STEP *** > merge from staging > Failed runner: nice make doc -j3 > See the log file log-staging-nice-make-doc--j3.txt > 09:54:57 Traceback (most recent call last): > File > "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", > line 523, in handle_staging > self.build (issue_id=issue_id) > File > "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", > line 328, 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 doc -j3 > See the log file log-staging-nice-make-doc--j3.txt
That one's mine, actually. GhostScript has thrown segfaults because of buffer overruns here, and what I pushed is not actually related to PostScript production. I tend to assign the fault to just having upgraded my version of Ubuntu and probably getting hit by a bad library. If someone else could check... -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel