Am 25. Mai 2015 15:18:46 MESZ, schrieb David Kastrup <d...@gnu.org>:
>pat...@gnu.org writes:
>
>> 12:38:14 (UTC) Begin LilyPond compile, previous commit at
> 2df342bbb164aeb3de0ec17304de90d178f1fd52
>> 12:38:18 test-master-lock and PID entry exist but previous Patchy
>> run (PID 10274) died, resetting test-master-lock anyway.
>> 12:38:19 Merged staging, now
>at: 2df342bbb164aeb3de0ec17304de90d178f1fd52
>> 12:38:20 Success: ./autogen.sh --noconfigure
>> 12:38:39 Success: /tmp/lilypond-autobuild/configure
>--enable-checking
>> 12:38:42 Success: nice make clean
>> 12:40:25 *** FAILED BUILD ***
>> nice make -j3 CPU_COUNT=3
>> Previous good commit: 68926767412d644f03b3200058baca5d8c929991
>> Current broken commit: 2df342bbb164aeb3de0ec17304de90d178f1fd52
>> 12:40:25 *** 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
>> 12:40:25 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
>
>Well yes: a patch of mine was not rewritten/rebased to correspond with
>an API change from Dan.
>
>Pushed a fixed variant to staging. I think it's been actually quite
>some time since we had our last breakage in staging...
I can't recall having seen such an email since I've subscribed to -devel.
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
