Re: Failed compiling a single lsr-snippet, which does not fail whenrunning the whole lsr
- Original Message - From: Thomas Morley thomasmorle...@googlemail.com To: lilypond-devel lilypond-devel@gnu.org Cc: David Nalesnik david.nales...@gmail.com; bug-lilypond bug-lilyp...@gnu.org Sent: Tuesday, April 03, 2012 12:26 AM Subject: Failed compiling a single lsr-snippet, which does not fail whenrunning the whole lsr Hi, Seba just informed me that the Contemporary vibrato snippet is not compiling. [snip] Do you think we should delete it and replace it with a working one when Mike completes it? -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed compiling a single lsr-snippet, which does not fail whenrunning the whole lsr
Am 3. April 2012 10:27 schrieb Phil Holmes m...@philholmes.net: - Original Message - From: Thomas Morley thomasmorle...@googlemail.com To: lilypond-devel lilypond-devel@gnu.org Cc: David Nalesnik david.nales...@gmail.com; bug-lilypond bug-lilyp...@gnu.org Sent: Tuesday, April 03, 2012 12:26 AM Subject: Failed compiling a single lsr-snippet, which does not fail whenrunning the whole lsr Hi, Seba just informed me that the Contemporary vibrato snippet is not compiling. [snip] Do you think we should delete it and replace it with a working one when Mike completes it? Yes. Can you do it or shall I ask Seba? But there is a very basic problem: If I test compiling the whole LSR and all is fine but compiling a single file from LSR failes, means I can't trust my testing-results. How can I continue the work? Having no chance to notice problematic files annoys me and in the end Seba, too. -Harm ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed compiling a single lsr-snippet, which does not fail whenrunning the whole lsr
- Original Message - From: Thomas Morley thomasmorle...@googlemail.com To: Phil Holmes m...@philholmes.net Cc: lilypond-devel lilypond-devel@gnu.org; David Nalesnik david.nales...@gmail.com; bug-lilypond bug-lilyp...@gnu.org Sent: Tuesday, April 03, 2012 11:53 AM Subject: Re: Failed compiling a single lsr-snippet, which does not fail whenrunning the whole lsr Am 3. April 2012 10:27 schrieb Phil Holmes m...@philholmes.net: - Original Message - From: Thomas Morley thomasmorle...@googlemail.com To: lilypond-devel lilypond-devel@gnu.org Cc: David Nalesnik david.nales...@gmail.com; bug-lilypond bug-lilyp...@gnu.org Sent: Tuesday, April 03, 2012 12:26 AM Subject: Failed compiling a single lsr-snippet, which does not fail whenrunning the whole lsr Hi, Seba just informed me that the Contemporary vibrato snippet is not compiling. [snip] Do you think we should delete it and replace it with a working one when Mike completes it? Yes. Can you do it or shall I ask Seba? I can do it and I've just done so. But there is a very basic problem: If I test compiling the whole LSR and all is fine but compiling a single file from LSR failes, means I can't trust my testing-results. How can I continue the work? Having no chance to notice problematic files annoys me and in the end Seba, too. -Harm We need to check what the script is doing and how it responds to failing snippets like this. I'm not in a position to do this right now, but let's not forget it's there. I've put it on the tracker as http://code.google.com/p/lilypond/issues/detail?id=2466 -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed compiling a single lsr-snippet, which does not fail whenrunning the whole lsr
On Apr 3, 2012, at 1:10 PM, Phil Holmes wrote: We need to check what the script is doing and how it responds to failing snippets like this. I'm not in a position to do this right now, but let's not forget it's there. I've put it on the tracker as http://code.google.com/p/lilypond/issues/detail?id=2466 It's also important to establish if this is a critical regression or not. The snippet dug into the bowels of LilyPond and used lots of functionality that's not put into play often. So its failure to compile may be pointing to an unexposed regression. Perhaps it'd be wise to label this as critical now and then downgrade it once we confirm that the compilation failure isn't coming from anything directly involved in running the LilyPond executable. Cheers, MS___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed compiling a single lsr-snippet, which does not fail whenrunning the whole lsr
On Tue, Apr 03, 2012 at 12:53:33PM +0200, Thomas Morley wrote: But there is a very basic problem: If I test compiling the whole LSR and all is fine but compiling a single file from LSR failes, means I can't trust my testing-results. How can I continue the work? Having no chance to notice problematic files annoys me and in the end Seba, too. Your method 1) here: http://lists.gnu.org/archive/html/lilypond-devel/2012-04/msg00056.html won't give any huge error messages if one lilypond run fails. You'll need to tweak that script to look at the returned value from lilypond and quit the entire script if it's a non-zero return value. I wouldn't expect method 2) to give much useful data; focus on adjusting method 1) so that it looks at the ret value. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed compiling a single lsr-snippet, which does not fail whenrunning the whole lsr
Am 3. April 2012 16:52 schrieb David Kastrup d...@gnu.org: m...@apollinemike.com m...@apollinemike.com writes: On Apr 3, 2012, at 1:10 PM, Phil Holmes wrote: We need to check what the script is doing and how it responds to failing snippets like this. I'm not in a position to do this right now, but let's not forget it's there. I've put it on the tracker as http://code.google.com/p/lilypond/issues/detail?id=2466 It's also important to establish if this is a critical regression or not. The snippet dug into the bowels of LilyPond and used lots of functionality that's not put into play often. So its failure to compile may be pointing to an unexposed regression. Perhaps it'd be wise to label this as critical now and then downgrade it once we confirm that the compilation failure isn't coming from anything directly involved in running the LilyPond executable. There are things like bleedover. See URL:http://code.google.com/p/lilypond/issues/detail?id=2449 for one example where a user interface was added that results in changes affecting the entire rest of a multi-file session. If a later snippet relies on a define-event-class in an earlier snippet, bleedover will make this reach into further sessions. git grep define-public Documentation/snippets returns several snippets that _export_ definitions (I have not checked whether this means that they will spill over, but I would not be surprised if it did). Any snippet that reaches into the bowels of LilyPond causing a _permanent_ change there surviving beyond the session is a mistake. It is possible that here one snippet depends on another snippet. What are the error messages in this particular case? -- David Kastrup I tried to narrow it down. At last I had only the contemporary-vibrato.ly-file in the directory. Using #!/bin/bash for LILYFILE in *.ly do STEM=$(basename $LILYFILE .ly) echo running $LILYFILE... lilypond --format=png -ddelete-intermediate-files $LILYFILE $STEM.txt done (as for the whole lsr) works and it compiles!! Compiling with 2.14.2 lilypond contemporary-vibrato.ly gave me simply: ERROR: Wrong type (expecting pair): () Can someone confirm this behaviour? I can hardly believe it. Compiling with 2.15.34 after removing a $-sign gave me contemporary-vibrato.ly:98:19: In procedure car in expression (map car in_l): contemporary-vibrato.ly:98:19: Wrong type (expecting pair): () Compiling with 2.12.3 works fine. Cheers, Harm ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed compiling a single lsr-snippet, which does not fail whenrunning the whole lsr
Thomas Morley thomasmorle...@googlemail.com writes: Using #!/bin/bash for LILYFILE in *.ly do STEM=$(basename $LILYFILE .ly) echo running $LILYFILE... lilypond --format=png -ddelete-intermediate-files $LILYFILE $STEM.txt done (as for the whole lsr) works and it compiles!! Compiling with 2.14.2 lilypond contemporary-vibrato.ly gave me simply: ERROR: Wrong type (expecting pair): () Can someone confirm this behaviour? I can hardly believe it. Compiling with 2.15.34 after removing a $-sign gave me contemporary-vibrato.ly:98:19: In procedure car in expression (map car in_l): contemporary-vibrato.ly:98:19: Wrong type (expecting pair): () Compiling with 2.12.3 works fine. Can you try with -dno-protected-scheme-parsing again? Sometimes this leads to better error messages. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed compiling a single lsr-snippet, which does not fail whenrunning the whole lsr
Am 3. April 2012 21:30 schrieb David Kastrup d...@gnu.org: Thomas Morley thomasmorle...@googlemail.com writes: Using #!/bin/bash for LILYFILE in *.ly do STEM=$(basename $LILYFILE .ly) echo running $LILYFILE... lilypond --format=png -ddelete-intermediate-files $LILYFILE $STEM.txt done (as for the whole lsr) works and it compiles!! Compiling with 2.14.2 lilypond contemporary-vibrato.ly gave me simply: ERROR: Wrong type (expecting pair): () Can someone confirm this behaviour? I can hardly believe it. Compiling with 2.15.34 after removing a $-sign gave me contemporary-vibrato.ly:98:19: In procedure car in expression (map car in_l): contemporary-vibrato.ly:98:19: Wrong type (expecting pair): () Compiling with 2.12.3 works fine. Can you try with -dno-protected-scheme-parsing again? Sometimes this leads to better error messages. -- David Kastrup Done. But I've got no additional message. -Harm ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
