Re: volunteer for patchy new-patches
As you can guess, that's the logfile produced when lily runs multiple jobs simultaneously. It also produces logfiles called something like multicpu0.log - look in the same directory for these - they'll have the most recent timestamp, too. Phil Holmes - Original Message - From: Marek Klein To: Julien Rioux Cc: lilypond-devel@gnu.org Sent: Tuesday, March 27, 2012 8:42 PM Subject: Re: volunteer for patchy new-patches 2012/3/27 Julien Rioux jri...@physics.utoronto.ca So it points to /tmp/lilypond-autobuild/build/out/lybook-testdb/snippet-names--7220266384705246370.log Is that file still around? http://gregoriana.sk/data/snippet-names--7220266384705246370.log Marek -- ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
Hi, 2012/3/23 Graham Percival gra...@percival-music.ca Well, you need to figure out why git fetch in your $LILYPOND_GIT repository fails. git fetch works now... I need som new patch for play with... Marek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
Marek, On 27 March 2012 18:48, Marek Klein ma...@gregoriana.sk wrote: Hi, 2012/3/23 Graham Percival gra...@percival-music.ca Well, you need to figure out why git fetch in your $LILYPOND_GIT repository fails. git fetch works now... I need som new patch for play with... Marek I reset one of mine on the countdown http://code.google.com/p/lilypond/issues/detail?id=2216 Try that. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
On 27/03/2012 1:48 PM, Marek Klein wrote: Hi, 2012/3/23 Graham Percivalgra...@percival-music.ca Well, you need to figure out why git fetch in your $LILYPOND_GIT repository fails. git fetch works now... I need som new patch for play with... Marek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel When there are no issues with a label of Patch=new, you can still test patches by specifying issue numbers on the command line like this: python test-patches.py 2216 without having to reset the said issue. -- Julien ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
2012/3/27 James pkx1...@gmail.com I reset one of mine on the countdown http://code.google.com/p/lilypond/issues/detail?id=2216 Try that. This is the output: Trying issue 2216 Found patch: (2216, '/home/marek/lilypond-patchy/issue5843060_6001.diff', 'AU: Document all options for lilypond -dhelp') Problem compiling master. Patchy cannot reliably continue. Traceback (most recent call last): File test-patches.py, line 16, in module main(issues_id) File test-patches.py, line 12, in main patchy.do_check(issues) File /home/marek/lilypond-patchy/projecthosting_patches.py, line 213, in do_check compile_lilypond_test.main(patches) File /home/marek/lilypond-patchy/compile_lilypond_test.py, line 289, in main raise err Exception: Failed runner: nice make test-baseline -j3 CPU_COUNT=3 See the log file log-None-nice-make-test-baseline--j3-CPU_COUNT=3.txt However, I cannot find the log file :( Marek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
On 27/03/2012 2:58 PM, Marek Klein wrote: 2012/3/27 Jamespkx1...@gmail.com I reset one of mine on the countdown http://code.google.com/p/lilypond/issues/detail?id=2216 Try that. This is the output: Trying issue 2216 Found patch: (2216, '/home/marek/lilypond-patchy/issue5843060_6001.diff', 'AU: Document all options for lilypond -dhelp') Problem compiling master. Patchy cannot reliably continue. Traceback (most recent call last): File test-patches.py, line 16, inmodule main(issues_id) File test-patches.py, line 12, in main patchy.do_check(issues) File /home/marek/lilypond-patchy/projecthosting_patches.py, line 213, in do_check compile_lilypond_test.main(patches) File /home/marek/lilypond-patchy/compile_lilypond_test.py, line 289, in main raise err Exception: Failed runner: nice make test-baseline -j3 CPU_COUNT=3 See the log file log-None-nice-make-test-baseline--j3-CPU_COUNT=3.txt However, I cannot find the log file :( Marek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel On a default configuration this logfile would be in /tmp/lilypond-autobuild Cheers, Julien ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
2012/3/27 Julien Rioux jri...@physics.utoronto.ca On 27/03/2012 2:58 PM, Marek Klein wrote: However, I cannot find the log file :( On a default configuration this logfile would be in /tmp/lilypond-autobuild Cheers, Julien Here it is: http://gregoriana.sk/data/log-None-nice-make-test-baseline--j3-CPU_COUNT=3.txt (The word Chyba means Error) Marek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
On 27/03/2012 3:20 PM, Marek Klein wrote: 2012/3/27 Julien Riouxjri...@physics.utoronto.ca On 27/03/2012 2:58 PM, Marek Klein wrote: However, I cannot find the log file :( On a default configuration this logfile would be in /tmp/lilypond-autobuild Cheers, Julien Here it is: http://gregoriana.sk/data/log-None-nice-make-test-baseline--j3-CPU_COUNT=3.txt (The word Chyba means Error) Marek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel So it points to /tmp/lilypond-autobuild/build/out/lybook-testdb/snippet-names--7220266384705246370.log Is that file still around? -- Julien ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
2012/3/27 Julien Rioux jri...@physics.utoronto.ca So it points to /tmp/lilypond-autobuild/build/**out/lybook-testdb/snippet- **names--7220266384705246370.log Is that file still around? http://gregoriana.sk/data/snippet-names--7220266384705246370.log Marek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
Marek, On 23 March 2012 21:42, Marek Klein ma...@gregoriana.sk wrote: 2012/3/23 Graham Percival gra...@percival-music.ca On Fri, Mar 23, 2012 at 10:31:20PM +0100, Marek Klein wrote: I've succeeded in building lilypond. :) test-patches.py says: No new patches to test. What are my next steps? I've just set issue 2216 to Patch-new, so try running it again. Trying issue 2216 Found patch: (2216, '/home/marek/lilypond-patchy/issue5843060_6001.diff', 'AU: Document all options for lilypond -dhelp') Traceback (most recent call last): File test-patches.py, line 16, in module main(issues_id) File test-patches.py, line 12, in main patchy.do_check(issues) File /home/marek/lilypond-patchy/projecthosting_patches.py, line 213, in do_check compile_lilypond_test.main(patches) File /home/marek/lilypond-patchy/compile_lilypond_test.py, line 282, in main autoCompile.prep_for_rietveld() File /home/marek/lilypond-patchy/compile_lilypond_test.py, line 140, in prep_for_rietveld self.update_git() File /home/marek/lilypond-patchy/compile_lilypond_test.py, line 112, in update_git run(git fetch) File /home/marek/lilypond-patchy/compile_lilypond_test.py, line 45, in run raise Exception(Command '%s' returned non-zero exit status %d\n%s % (cmd, returncode, stderr.strip())) Exception: Command 'git fetch' returned non-zero exit status 128 error: insufficient permission for adding an object to repository database .git/objects fatal: failed to write object fatal: unpack-objects failed Did you get it working yet? It seems that permissions to your $LILYPOND_GIT location or who you are running the script as are not allowed to 'git fetch' and pull down any changes from the current code to apply the patch to then check it. Either you need to change the permissions somewhere (probably unlikely) or you need to edit the files further to make sure that the scripts are trying to 'fetch' the most up to date branch to the correct place. If you can let us know if you 1. Edited any of the files before you tried to run the scripts 2. If your %LILYPOND_GIT location is set - if you use LilyDev it should already be set for you. Regards James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
I've succeeded in building lilypond. :) test-patches.py says: No new patches to test. What are my next steps? Marek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
On Fri, Mar 23, 2012 at 10:31:20PM +0100, Marek Klein wrote: I've succeeded in building lilypond. :) test-patches.py says: No new patches to test. What are my next steps? I've just set issue 2216 to Patch-new, so try running it again. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
On Fri, Mar 23, 2012 at 10:42:54PM +0100, Marek Klein wrote: Exception: Command 'git fetch' returned non-zero exit status 128 error: insufficient permission for adding an object to repository database .git/objects fatal: failed to write object fatal: unpack-objects failed Well, you need to figure out why git fetch in your $LILYPOND_GIT repository fails. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
Hi, 2012/3/16 Graham Percival gra...@percival-music.ca On Fri, Mar 16, 2012 at 09:52:52PM +0100, Marek Klein wrote: I can do it, I think (almost every day). Great! Here's the link to get started: http://lilypond.org/doc/v2.15/Documentation/contributor/patchy ... although apparently that doesn't include a link to the actual code. huh. https://github.com/gperciva/lilypond-extra - Graham what are the next steps? Should I try to run python lilypond-patchy-staging.py ? Marek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
On 20/03/2012 4:26 PM, Marek Klein wrote: Hi, 2012/3/16 Graham Percivalgra...@percival-music.ca On Fri, Mar 16, 2012 at 09:52:52PM +0100, Marek Klein wrote: I can do it, I think (almost every day). Great! Here's the link to get started: http://lilypond.org/doc/v2.15/Documentation/contributor/patchy ... although apparently that doesn't include a link to the actual code. huh. https://github.com/gperciva/lilypond-extra - Graham what are the next steps? Should I try to run python lilypond-patchy-staging.py ? Marek python test-patches.py -- Julien ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
2012/3/20 Julien Rioux jri...@physics.utoronto.ca python test-patches.py This is the result: Trying issue 2272 Found patch: (2272, '/home/marek/lilypond-patchy/issue5843063_7.diff', 'Long monosyllabic words collide with barlines') Problem compiling master. Patchy cannot reliably continue. Traceback (most recent call last): File test-patches.py, line 16, in module main(issues_id) File test-patches.py, line 12, in main patchy.do_check(issues) File /home/marek/lilypond-patchy/projecthosting_patches.py, line 213, in do_check compile_lilypond_test.main(patches) File /home/marek/lilypond-patchy/compile_lilypond_test.py, line 289, in main raise err Exception: Failed runner: ./autogen.sh --noconfigure See the log file log-None-autogen.sh.txt ? Marek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
On Tue, Mar 20, 2012 at 10:48:57PM +0100, Marek Klein wrote: Exception: Failed runner: ./autogen.sh --noconfigure See the log file log-None-autogen.sh.txt Well, what's in the log file log-None-autgen.sh.txt ? It's in the build directory. This whole infrastructure assumes that you can compile lilypond normally; if there's a problem in autogen.sh, it seems like you don't have autotools installed. You may want to consider trying out lilydev instead of manually installing all required dependencies. It depends on how familiar you are with linux. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
Graham Percival gra...@percival-music.ca writes: On Tue, Mar 20, 2012 at 10:48:57PM +0100, Marek Klein wrote: Exception: Failed runner: ./autogen.sh --noconfigure See the log file log-None-autogen.sh.txt Well, what's in the log file log-None-autgen.sh.txt ? It's in the build directory. This whole infrastructure assumes that you can compile lilypond normally; if there's a problem in autogen.sh, it seems like you don't have autotools installed. You may want to consider trying out lilydev instead of manually installing all required dependencies. It depends on how familiar you are with linux. sudo apt-get build-dep lilypond should get you pretty far regarding having the required build dependencies installed on dpkg-based systems. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
Hello,
On 16 March 2012 21:30, Graham Percival gra...@percival-music.ca wrote:
On Fri, Mar 16, 2012 at 05:28:21PM -0400, Julien Rioux wrote:
On 16/03/2012 4:55 PM, Graham Percival wrote:
... although apparently that doesn't include a link to the actual
code. huh.
https://github.com/gperciva/lilypond-extra
No?
http://lilypond.org/doc/v2.15/Documentation/contributor/patchy#Installing-patchy
oh, huh. My eyes skipped over it because it wasn't blue.
Anybody feel like wrapping that in a @uref{} ? If so, please push
directly to staging.
Voila!
committer James Lowe pkx1...@gmail.com
Sat, 17 Mar 2012 16:19:17 + (16:19 +)
commit ddc638764124c27750baf39b4c42f7f6d0061a15
--
--
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
I'm working with the University of Paris VIII to get a computer consecrated to the cause. Once that happens, we'll have a new patchy platform. It's also good to have that sorta institutional alliance when it comes to applying to stuff like GSoC. Cheers, MS On Mar 16, 2012, at 8:41 PM, Graham Percival wrote: I think it's high time for somebody else to run the new-patches test. For this task, David is ridiculously overqualified, but his laptop is pretty underqualified. That combination makes him almost the worst person to run this task. I'm hoping that this won't end up with James doing it; IMO even James is overqualified to be running patchy new-patches. But maybe that would be ok for a week or two, in order to catch some more gotchas in the script and docs, then pass it on to another person. Maybe one of the bug squad members? NB: this is *not* a review, nor does it require any knowledge of lilypond programming at all. You run a script, if it finishes then you look at some pictures and then say nope, no change to the pictures. Once you have the script set up -- which is easier than the patchy staging-merge, BTW -- it's easier than being a bug squad member! On a more general note, I've love it if we could start foisting off some more development/maintenace tasks onto the current bug squad members, and start recruiting some new bug squad members to replace the existing ones. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
On Sat, Mar 17, 2012 at 9:03 PM, m...@apollinemike.com wrote: I'm working with the University of Paris VIII to get a computer consecrated to the cause. Once that happens, we'll have a new patchy platform. It's also good to have that sorta institutional alliance when it comes to applying to stuff like GSoC. Cool! Great idea, thanks! Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
volunteer for patchy new-patches
I think it's high time for somebody else to run the new-patches test. For this task, David is ridiculously overqualified, but his laptop is pretty underqualified. That combination makes him almost the worst person to run this task. I'm hoping that this won't end up with James doing it; IMO even James is overqualified to be running patchy new-patches. But maybe that would be ok for a week or two, in order to catch some more gotchas in the script and docs, then pass it on to another person. Maybe one of the bug squad members? NB: this is *not* a review, nor does it require any knowledge of lilypond programming at all. You run a script, if it finishes then you look at some pictures and then say nope, no change to the pictures. Once you have the script set up -- which is easier than the patchy staging-merge, BTW -- it's easier than being a bug squad member! On a more general note, I've love it if we could start foisting off some more development/maintenace tasks onto the current bug squad members, and start recruiting some new bug squad members to replace the existing ones. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
2012/3/16 Graham Percival gra...@percival-music.ca On Fri, Mar 16, 2012 at 09:00:48PM +0100, Marek Klein wrote: Hello, 2012/3/16 Graham Percival gra...@percival-music.ca ... You run a script, if it finishes then you look at some pictures and then say nope, no change to the pictures. Once you have the script set up -- which is easier than the patchy staging-merge, BTW -- it's easier than being a bug squad member! ... How often does it have to be done? At what time?... Once a day would be good, but it doesn't always need to be the same person. I mean, you could do it twice a week or something, with other people doing it on the other days? - Graham I can do it, I think (almost every day). Marek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
On Fri, Mar 16, 2012 at 09:52:52PM +0100, Marek Klein wrote: I can do it, I think (almost every day). Great! Here's the link to get started: http://lilypond.org/doc/v2.15/Documentation/contributor/patchy ... although apparently that doesn't include a link to the actual code. huh. https://github.com/gperciva/lilypond-extra - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
On 16/03/2012 4:55 PM, Graham Percival wrote: On Fri, Mar 16, 2012 at 09:52:52PM +0100, Marek Klein wrote: I can do it, I think (almost every day). Great! Here's the link to get started: http://lilypond.org/doc/v2.15/Documentation/contributor/patchy ... although apparently that doesn't include a link to the actual code. huh. https://github.com/gperciva/lilypond-extra - Graham No? http://lilypond.org/doc/v2.15/Documentation/contributor/patchy#Installing-patchy -- Julien ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
On Fri, Mar 16, 2012 at 05:28:21PM -0400, Julien Rioux wrote:
On 16/03/2012 4:55 PM, Graham Percival wrote:
... although apparently that doesn't include a link to the actual
code. huh.
https://github.com/gperciva/lilypond-extra
No?
http://lilypond.org/doc/v2.15/Documentation/contributor/patchy#Installing-patchy
oh, huh. My eyes skipped over it because it wasn't blue.
Anybody feel like wrapping that in a @uref{} ? If so, please push
directly to staging.
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
