Re: Patchy email from PhilH

[David Kastrup]

"Phil Holmes" <address@hidden> writes:

> ----- Original Message ----- 
> From: "David Kastrup" <address@hidden>
> To: <address@hidden>
> Sent: Friday, October 05, 2012 4:55 PM
> Subject: Re: Patchy email from PhilH
>
>
>> "Phil Holmes" <address@hidden> writes:
>>
>>> ----- Original Message ----- 
>>> From: <address@hidden>
>>> To: <address@hidden>
>>> Cc: <address@hidden>
>>> Sent: Friday, October 05, 2012 4:11 PM
>>> Subject: Patchy email from PhilH
>>>
>>>
>>>> Begin LilyPond compile, commit: 4ed5d7710416aff0a9e68f0d751b4e15c30fdf92
>>>>
>>>> Merged staging, now at: c9d806f28ab690c3f210e14153c6bd31d506588e
>>>>
>>>> Success: ./autogen.sh --noconfigure
>>>>
>>>> Success: ../configure --disable-optimising
>>>>
>>>> Success: nice make clean -j9 CPU_COUNT=9 -s
>>>>
>>>> Success: nice make -j9 CPU_COUNT=9 -s
>>>>
>>>> Success: nice make test -j9 CPU_COUNT=9 -s
>>>>
>>>> *** FAILED BUILD ***
>>>>
>>>> nice make doc -j9 CPU_COUNT=9 -s
>>>>
>>>> Previous good commit: 4ed5d7710416aff0a9e68f0d751b4e15c30fdf92
>>>>
>>>> Current broken commit: c9d806f28ab690c3f210e14153c6bd31d506588e
>>>
>>> This is the error:
>>>
>>> Processing
>>> /media/IntelSSD/patchybuild/autobuild/build/out/lybook-db/61/lily-1564b6f0.ly'
>>> Parsing...
>>> /media/IntelSSD/patchybuild/autobuild/build/out/lybook-db/61/lily-1564b6f0.ly:144:7:
>>> error: wrong type for argument 1.  Expecting list, found "Slur"
>>> \shape
>>>       Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0))
>>> /media/IntelSSD/patchybuild/autobuild/build/out/lybook-db/61/lily-1564b6f0.ly:144:12:
>>> error: wrong type for argument 2.  Expecting string or music, found
>>> ((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0))
>>> \shape Slur
>>>            #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0))
>>> Interpreting music...
>>>
>>> [snip]
>>>
>>> fatal error: failed files: "61/lily-1564b6f0.ly"
>>>
>>> I presume 220f439edbd95266113248a984ebe6c4b97dcf14 is the culprit.
>>
>> Huh.  This should have been caught by running convert-ly and I have no
>> idea why it didn't.  I'll back the shape change out of staging (rebasing
>> the other commits in the process) and investigate what went wrong here.
>>
>> It is quite strange since a number of very similar lines converted just
>> fine.
>>
>> -- 
>> David Kastrup
>
>
> Do you need any more info on the identity of the failing file?

No.  git grep works just fine for finding those.  It is more than one.

-- 
David Kastrup