pat...@gnu.org writes:
> 07:02:37 (UTC) Begin LilyPond compile, previous commit at
> 52c98e2ec5f3ef2a24ee1a2d94dd09f8517a6f36
> 07:02:40 Merged staging, now at: 52c98e2ec5f3ef2a24ee1a2d94dd09f8517a6f36
> 07:02:41 Success: ./autogen.sh --noconfigure
> 07:02:57 Success: /tmp/lilypond-autobuild/configure
> --enable-checking
> 07:02:59 Success: nice make clean
> 07:06:51 *** FAILED BUILD ***
> nice make -j9 CPU_COUNT=9
> Previous good commit: 1272e45b49fb91fb5fd181b7d045a0ac4d662450
> Current broken commit: 52c98e2ec5f3ef2a24ee1a2d94dd09f8517a6f36
> 07:06:51 *** FAILED STEP ***
> merge from staging
> Failed runner: nice make -j9 CPU_COUNT=9
> See the log file log-staging-nice-make--j9-CPU_COUNT=9.txt
> 07:06:51 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 -j9 CPU_COUNT=9
> See the log file log-staging-nice-make--j9-CPU_COUNT=9.txt
The relevant line:
lilypond-book.py: error: file not found: turkish-makam-example.ly
Most likely this built on the committer's computer because this file was
locally present but not checked into the version control system.
I'll be backing that commit out of staging.
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
