David,
On 21 December 2012 16:22, Phil Holmes <m...@philholmes.net> wrote:
> ----- Original Message ----- From: "Phil Holmes" <m...@philholmes.net>
> To: "James" <pkx1...@gmail.com>; <lilypond-devel@gnu.org>
> Cc: <lilypond-a...@gnu.org>
> Sent: Friday, December 21, 2012 4:05 PM
>
> Subject: Re: Patchy email
>
>
>> ----- Original Message ----- From: "James" <pkx1...@gmail.com>
>> To: <lilypond-devel@gnu.org>
>> Cc: <lilypond-a...@gnu.org>
>> Sent: Friday, December 21, 2012 3:57 PM
>> Subject: Re: Patchy email
>>
>>
>>> Hello
>>>
>>> On 21 December 2012 15:52, <philehol...@googlemail.com> wrote:
>>>>
>>>> 15:43:05 (UTC) Begin LilyPond compile, previous commit at
>>>> 2c646d632acf0cf1d08a4843de5d536a34a7e2da
>>>> 15:43:13 From ssh://git.sv.gnu.org/srv/git/lilypond
>>>> 2c646d6..4c4c59a master -> origin/master
>>>> 2c646d6..37ac57f staging -> origin/staging
>>>> cb05c49..2865242 translation -> origin/translation
>>>> 15:43:20 Merged staging, now at:
>>>> 37ac57f59e452b5c1d84f466edadcc195db99b5a
>>>> 15:43:20 Success: ./autogen.sh --noconfigure
>>>> 15:43:33 Success: /home/patchy/patchybuild/autobuild/configure
>>>> --disable-optimising
>>>> 15:43:37 Success: nice make clean
>>>> 15:44:36 Success: nice make -j9 CPU_COUNT=9 -s
>>>> 15:46:39 Success: nice make test -j9 CPU_COUNT=9
>>>> -s
>>>> 15:52:34 *** FAILED BUILD ***
>>>> nice make doc -j9 CPU_COUNT=9 -s
>>>> Previous good commit: 2c646d632acf0cf1d08a4843de5d536a34a7e2da
>>>> Current broken commit: 37ac57f59e452b5c1d84f466edadcc195db99b5a
>>>> 15:52:34 *** FAILED STEP ***
>>>> merge from staging
>>>> Failed runner: nice make doc -j9 CPU_COUNT=9 -s
>>>> See the log file log-staging-nice-make-doc--j9-CPU_COUNT=9--s.txt
>>>> 15:52:34 Traceback (most recent call last):
>>>> File
>>>> "/home/patchy/lilypond-extra/patches/compile_lilypond_test/__init__.py",
>>>> line 523, in handle_staging
>>>> self.build (issue_id=issue_id)
>>>> File
>>>> "/home/patchy/lilypond-extra/patches/compile_lilypond_test/__init__.py",
>>>> line 328, in build
>>>> issue_id)
>>>> File
>>>> "/home/patchy/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 -j9 CPU_COUNT=9 -s
>>>> See the log file log-staging-nice-make-doc--j9-CPU_COUNT=9--s.txt
>>>>
>>>> _______________________________________________
>>>
>>>
>>> That'll be why then.
>>>
>>> I haven't enabled patchy on my side to send the email when it fails,
>>> although I still cannot access my server remotely.
>>>
>>> James
>>
>>
>>
>> I've almost debugged the problem. Will report soon.
>
>
> The problem occurs as:
>
> warning: do not know how to interpret articulation:
> warning: scheme encoding:
> "thumb"[8]
> Preprocessing graphical objects...lilypond:
> /home/patchy/patchybuild/autobuild/lily/script-interface.cc:36: static
> Stencil Script_interface::get_stencil(Grob*, Direction): Assertion
> `ly_is_pair (s)' failed.
> Aborted
>
> This is in the notation appendix, A.13 - see
> http://lilypond.org/doc/v2.17/Documentation/notation/list-of-articulations#instrument_002dspecific-scripts
>
> I think I have to suspect
> http://code.google.com/p/lilypond/issues/detail?id=1029
>
> I guess script-chart.ly needs amending to remove thumb from the list of
> instrument specific scripts.
Looks like leaving test-patchy configured to build doc is going to be
a good thing :)
Was this one that was 'passed' before I enabled it yesterday?
James
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
