pat...@gnu.org writes:
> 10:35:41 (UTC) Begin LilyPond compile, previous commit at
> def633f7a88fe8950b685adee93165c42299bd5c
> 10:35:55 Merged staging, now at: def633f7a88fe8950b685adee93165c42299bd5c
> 10:35:56 Success: ./autogen.sh --noconfigure
> 10:36:13 Success: /tmp/lilypond-autobuild/configure
> --disable-optimising
> 10:36:17 Success: nice make clean
> 10:42:40 Success: nice make -j3 CPU_COUNT=3
> 10:50:35 *** FAILED BUILD ***
> nice make test -j3 CPU_COUNT=3
> Previous good commit: a1467ba6de6240dda93009c907b05794ec9b8d54
> Current broken commit: def633f7a88fe8950b685adee93165c42299bd5c
> 10:50:35 *** FAILED STEP ***
> merge from staging
> Failed runner: nice make test -j3 CPU_COUNT=3
> See the log file log-staging-nice-make-test--j3-CPU_COUNT=3.txt
> 10:50:35 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 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 test -j3 CPU_COUNT=3
> See the log file log-staging-nice-make-test--j3-CPU_COUNT=3.txt
Ugh. The Python module. If I compile that with 64bit, it won't
cooperate with my 32bit Python2.7. And half the desktop environment
depends on that so I don't want to swap that out.
I have to see whether I can make a clean 64/32 split along the necessary
lines here.
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
