Patchy email
Begin LilyPond compile, commit: 05efb98f2e3ff68f4bb8221db640b0174bfcde93 Merged staging, now at: b445e1b4207996eee2362187fa3e8b8af8ff05ba Success:./autogen.sh --noconfigure Success:../configure --disable-optimising Success:nice make clean -j3 CPU_COUNT=3 Success:nice make -j3 CPU_COUNT=3 *** FAILED BUILD *** nice make test -j3 CPU_COUNT=3 Previous good commit: 05efb98f2e3ff68f4bb8221db640b0174bfcde93 Current broken commit: b445e1b4207996eee2362187fa3e8b8af8ff05ba ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
On Sat, Jan 28, 2012 at 04:18:00AM -0800, lilypond.patchy.gra...@gmail.com wrote: *** FAILED BUILD *** nice make test -j3 CPU_COUNT=3 Previous good commit: 05efb98f2e3ff68f4bb8221db640b0174bfcde93 Current broken commit: b445e1b4207996eee2362187fa3e8b8af8ff05ba make[1]: *** [out-test/tex-fragment.tex] Error 1 make[1]: *** Waiting for unfinished jobs - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
updated git-cl
there's an improved git-cl on my github account now: https://github.com/gperciva/git-cl Thanks to Lukasz Czerwinski, it tracks all lilypond patches with the same base url. http://codereview.appspot.com/search?base=http://git.savannah.gnu.org/gitweb/?p=lilypond.git/trunk/ All contributors are still urged to allow git-cl to make an issue in the code.google.com issue tracker, but it's nice to have an extra layer of security. I suggest that everybody updates their git-cl repo. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
On Sat, Jan 28, 2012 at 7:27 AM, Graham Percival gra...@percival-music.ca wrote: On Sat, Jan 28, 2012 at 04:18:00AM -0800, lilypond.patchy.gra...@gmail.com wrote: *** FAILED BUILD *** nice make test -j3 CPU_COUNT=3 Previous good commit: 05efb98f2e3ff68f4bb8221db640b0174bfcde93 Current broken commit: b445e1b4207996eee2362187fa3e8b8af8ff05ba make[1]: *** [out-test/tex-fragment.tex] Error 1 make[1]: *** Waiting for unfinished jobs - Graham Is there more to the log? I cannot reproduce the failure. -- Julien ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
Julien, On 28 January 2012 13:31, Julien Rioux julien.ri...@gmail.com wrote: On Sat, Jan 28, 2012 at 7:27 AM, Graham Percival gra...@percival-music.ca wrote: On Sat, Jan 28, 2012 at 04:18:00AM -0800, lilypond.patchy.gra...@gmail.com wrote: *** FAILED BUILD *** nice make test -j3 CPU_COUNT=3 Previous good commit: 05efb98f2e3ff68f4bb8221db640b0174bfcde93 Current broken commit: b445e1b4207996eee2362187fa3e8b8af8ff05ba make[1]: *** [out-test/tex-fragment.tex] Error 1 make[1]: *** Waiting for unfinished jobs - Graham I don't use patchy but checking out staging just now, I run ./configure ; make -j8 CPU_COUNT=8 ; This was all fine. When I ran make doc (make -j8 CPU_COUNT=8 doc) it 'nearly' completed. The last lot of log I got was --snip-- Success: compilation successfully completed Writing /home/james/lilypond-git/build/out/lybook-db/05/lily-f58ad554-1.signature Layout output to `/home/james/lilypond-git/build/out/lybook-db/05/lily-f58ad554.eps'... Converting to `/home/james/lilypond-git/build/out/lybook-db/05/lily-f58ad554.pdf'... Layout output to `/home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-1.eps'... Converting to `/home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-1.pdf'... Preprocessing graphical objects... Layout output to `/home/james/lilypond-git/build/out/lybook-db/30/lily-10fcfa18-1.eps'... Could not overwrite file /home/james/lilypond-git/build/input/regression/lilypond-book/out-www/08/lily-015b46b4.png Converting to `/home/james/lilypond-git/build/out/lybook-db/30/lily-10fcfa18-1.pdf'... make[4]: *** [out-www/html-space-after-tag.html] Error 1 Layout output to `/home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-1.eps'... Converting to `/home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-1.pdf'... Calculating line breaks... Drawing systems... Writing /home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-systems.texi... Writing /home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-systems.tex... Writing /home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-systems.count...Converting to PNG... Writing /home/james/lilypond-git/build/out/lybook-db/fa/lily-a6ab8ae4-1.signature Layout output to `/home/james/lilypond-git/build/out/lybook-db/fa/lily-a6ab8ae4.eps'... Converting to `/home/james/lilypond-git/build/out/lybook-db/fa/lily-a6ab8ae4.pdf'... Writing /home/james/lilypond-git/build/out/lybook-db/30/lily-10fcfa18-systems.texi... Writing /home/james/lilypond-git/build/out/lybook-db/30/lily-10fcfa18-systems.tex... Writing /home/james/lilypond-git/build/out/lybook-db/30/lily-10fcfa18-systems.count...Writing /home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-systems.texi... Writing /home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-systems.tex... Writing /home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-systems.count... Success: compilation successfully completed Layout output to `/home/james/lilypond-git/build/out/lybook-db/05/lily-f58ad554-1.eps'... Converting to `/home/james/lilypond-git/build/out/lybook-db/05/lily-f58ad554-1.pdf'... Success: compilation successfully completed Converting to PNG... Success: compilation successfully completed Writing /home/james/lilypond-git/build/out/lybook-db/05/lily-f58ad554-systems.texi... Writing /home/james/lilypond-git/build/out/lybook-db/05/lily-f58ad554-systems.tex... Writing /home/james/lilypond-git/build/out/lybook-db/05/lily-f58ad554-systems.count... Layout output to `/home/james/lilypond-git/build/out/lybook-db/fa/lily-a6ab8ae4-1.eps'... Success: compilation successfully completed Converting to `/home/james/lilypond-git/build/out/lybook-db/fa/lily-a6ab8ae4-1.pdf'... Writing /home/james/lilypond-git/build/out/lybook-db/fa/lily-a6ab8ae4-systems.texi... Writing /home/james/lilypond-git/build/out/lybook-db/fa/lily-a6ab8ae4-systems.tex... Writing /home/james/lilypond-git/build/out/lybook-db/fa/lily-a6ab8ae4-systems.count... Success: compilation successfully completed make[4]: Leaving directory `/home/james/lilypond-git/build/input/regression/lilypond-book' make[3]: *** [WWW-1] Error 2 make[3]: Leaving directory `/home/james/lilypond-git/build/input/regression' make[2]: *** [WWW-1] Error 2 make[2]: Leaving directory `/home/james/lilypond-git/build/input' make[1]: *** [WWW-1] Error 2 make[1]: Leaving directory `/home/james/lilypond-git/build' make: *** [doc-stage-1] Error 2 james@jameslilydev2:~/lilypond-git/build$ --snip-- Hope this helps. james -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
On Sat, Jan 28, 2012 at 08:31:04AM -0500, Julien Rioux wrote: On Sat, Jan 28, 2012 at 7:27 AM, Graham Percival gra...@percival-music.ca wrote: On Sat, Jan 28, 2012 at 04:18:00AM -0800, lilypond.patchy.gra...@gmail.com wrote: make[1]: *** [out-test/tex-fragment.tex] Error 1 make[1]: *** Waiting for unfinished jobs Is there more to the log? I cannot reproduce the failure. Not that I can tell. :( remember that we still have all 3 jobs outputting info to the same logfile, so it's pretty confused. I'll send you the entire log privately just in case you can find anything interesting. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
On Sat, Jan 28, 2012 at 8:58 AM, James pkx1...@gmail.com wrote: Julien, On 28 January 2012 13:31, Julien Rioux julien.ri...@gmail.com wrote: On Sat, Jan 28, 2012 at 7:27 AM, Graham Percival gra...@percival-music.ca wrote: On Sat, Jan 28, 2012 at 04:18:00AM -0800, lilypond.patchy.gra...@gmail.com wrote: *** FAILED BUILD *** nice make test -j3 CPU_COUNT=3 Previous good commit: 05efb98f2e3ff68f4bb8221db640b0174bfcde93 Current broken commit: b445e1b4207996eee2362187fa3e8b8af8ff05ba make[1]: *** [out-test/tex-fragment.tex] Error 1 make[1]: *** Waiting for unfinished jobs - Graham I don't use patchy but checking out staging just now, I run ./configure ; make -j8 CPU_COUNT=8 ; This was all fine. When I ran make doc (make -j8 CPU_COUNT=8 doc) it 'nearly' completed. The last lot of log I got was --snip-- Success: compilation successfully completed Writing /home/james/lilypond-git/build/out/lybook-db/05/lily-f58ad554-1.signature Layout output to `/home/james/lilypond-git/build/out/lybook-db/05/lily-f58ad554.eps'... Converting to `/home/james/lilypond-git/build/out/lybook-db/05/lily-f58ad554.pdf'... Layout output to `/home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-1.eps'... Converting to `/home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-1.pdf'... Preprocessing graphical objects... Layout output to `/home/james/lilypond-git/build/out/lybook-db/30/lily-10fcfa18-1.eps'... Could not overwrite file /home/james/lilypond-git/build/input/regression/lilypond-book/out-www/08/lily-015b46b4.png Thanks. Are there known issues about running multiple lilypond-book instances in parallel when they touch the same files? I'm guessing this is what's going on because a lot of the test files input the same snippets as example, which would have identical generated filenames. -- Julien ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
On Sat, Jan 28, 2012 at 09:07:12AM -0500, Julien Rioux wrote: Thanks. Are there known issues about running multiple lilypond-book instances in parallel when they touch the same files? I'm guessing this is what's going on because a lot of the test files input the same snippets as example, which would have identical generated filenames. I can't think of any such issues off the top of my head, but I wouldn't be surprised if there were unknown issues about this. oh wait, I *do* remember something arises from the translations: the documentation has multiple copies of the same .ly file in various translations. The whole reason we have a out/lybook-db/ is to try to notice idential filenames and avoid rewriting them. A few years ago (sorry... between 2 and 5 years is as much as I can narrow it down from memory, and a few quick searches of -devel didn't pinpoint anything) that was a serious problem with doc compiles. actually, a quick look at the history for make/lydocs-make suggests 3a9c1df02fdb6846418c5794a7b04d07209e95b3 and I definitely remember that John Mandereau was working on this stuff. It would fit the time span. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
On Sat, Jan 28, 2012 at 9:14 AM, Graham Percival gra...@percival-music.ca wrote: On Sat, Jan 28, 2012 at 09:07:12AM -0500, Julien Rioux wrote: Thanks. Are there known issues about running multiple lilypond-book instances in parallel when they touch the same files? I'm guessing this is what's going on because a lot of the test files input the same snippets as example, which would have identical generated filenames. I can't think of any such issues off the top of my head, but I wouldn't be surprised if there were unknown issues about this. oh wait, I *do* remember something arises from the translations: the documentation has multiple copies of the same .ly file in various translations. The whole reason we have a out/lybook-db/ is to try to notice idential filenames and avoid rewriting them. A few years ago (sorry... between 2 and 5 years is as much as I can narrow it down from memory, and a few quick searches of -devel didn't pinpoint anything) that was a serious problem with doc compiles. actually, a quick look at the history for make/lydocs-make suggests 3a9c1df02fdb6846418c5794a7b04d07209e95b3 and I definitely remember that John Mandereau was working on this stuff. It would fit the time span. - Graham I'll have to test again with -j3, sorry. I suggest we erase the last two commits from staging until this is resolved. The convert-ly commit should be pretty safe. Is there a git doctor in the room? Julien ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
On Sat, Jan 28, 2012 at 09:18:03AM -0500, Julien Rioux wrote: I'll have to test again with -j3, sorry. I suggest we erase the last two commits from staging until this is resolved. The convert-ly commit should be pretty safe. oh, I did that an hour ago, and Patchy's finished merging it now. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Plans for changing chord repeat implementations
Nicolas Sceaux nicolas.sce...@gmail.com writes: Le 26 janv. 2012 à 11:00, David Kastrup a écrit : The bad news is that absolute pitch friends would have to call the \q function (any better name for it?) explicitly. Since q is an input convenience, and relative pitch is also an input convenience, I don't think that there would be much of an affected user base. I do use absolute pitch mode, together with the q shortcut, so the affected user base is non-nil. URL:http://codereview.appspot.com/5595043 What would be the impact of your solution on this kind of code? Is it just about adding e.g. \q before the block? The user impact is now down to nil. There is no longer any relation of the implementation to \relative. Since you don't need to call it manually except for special considerations (like letting it retain articulations in some passage), \q is now called \chordRepeats. I don't think that there are nightmarish corners in the implementation and behavior any more. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
