Re: New Patchy thread
- Original Message - From: "James" Well once I get some nice 1, 2, 3 instructions I can run patchy 24/7. Will do. It's actually pretty simple. I've had to refocus on outstanding Doc tracker issues and Patchy seems to have moved on since two weeks back. Frankly I need the heat in my study ;) Check the temperature in my study here: http://www.philholmes.net/weather/ The little blip in the humidity indoors was my cup of coffee :-) -- James -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New Patchy thread
Hello, On 31 January 2012 14:05, Phil Holmes wrote: > - Original Message - From: "Graham Percival" > > To: "Phil Holmes" > Cc: "David Kastrup" ; > Sent: Tuesday, January 31, 2012 1:56 PM > > Subject: Re: New Patchy thread > > >> On Tue, Jan 31, 2012 at 01:47:52PM -, Phil Holmes wrote: >>> >>> There you go. That seemed to work. >> >> >> Yep, looks good. >> >>> I assume all I need to do is run patchy-staging daily? >> >> >> Yes and no. Running it daily would be great. Running it every 12 >> hours might be nicer, although maybe you could alternate with >> James or Reinhold? > > > I'll see how we go. It might be a breakfast and tea job. > > >> Another thing to consider is setting up a cronjob. Instead of >> running it manually, if your computer is always on, it'll just do >> its thing by itself. Great for 4am in the morning! > > > Can't afford the electric! Might see if I can work out how to wake the > computer, run patchy, and go back to sleep. Don't think I could run it at > night though - my study's next door to the bedroom and the fans would > probably wake us up > Well once I get some nice 1, 2, 3 instructions I can run patchy 24/7. I've had to refocus on outstanding Doc tracker issues and Patchy seems to have moved on since two weeks back. Frankly I need the heat in my study ;) -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New Patchy thread
- Original Message - From: "Graham Percival" To: "Phil Holmes" Cc: "David Kastrup" ; Sent: Tuesday, January 31, 2012 1:56 PM Subject: Re: New Patchy thread On Tue, Jan 31, 2012 at 01:47:52PM -, Phil Holmes wrote: There you go. That seemed to work. Yep, looks good. I assume all I need to do is run patchy-staging daily? Yes and no. Running it daily would be great. Running it every 12 hours might be nicer, although maybe you could alternate with James or Reinhold? I'll see how we go. It might be a breakfast and tea job. Another thing to consider is setting up a cronjob. Instead of running it manually, if your computer is always on, it'll just do its thing by itself. Great for 4am in the morning! Can't afford the electric! Might see if I can work out how to wake the computer, run patchy, and go back to sleep. Don't think I could run it at night though - my study's next door to the bedroom and the fans would probably wake us up -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New Patchy thread
On Tue, Jan 31, 2012 at 01:47:52PM -, Phil Holmes wrote: > There you go. That seemed to work. Yep, looks good. > I assume all I need to do is run patchy-staging daily? Yes and no. Running it daily would be great. Running it every 12 hours might be nicer, although maybe you could alternate with James or Reinhold? Note that if there's no new patches, Patchy staging-merge just quits and tells you there's nothing to do, so don't worry about it wasting resources compiling exactly the same thing over and over again. That said, if there's a one-line typo fix in the docs, it'll still rebuild absolutely everything. Another thing to consider is setting up a cronjob. Instead of running it manually, if your computer is always on, it'll just do its thing by itself. Great for 4am in the morning! Finally, occasionally staging breaks. That'll show up in the logs in your lilypond-patch-build-output-log-directory, or if you set up the mail stuff, you'll get an email warning you about the problem. When there's a problem it requires manual attention (although not necessarily from you, and it's theoretically possible to make patchy take care of this automatically, but that's a far-off idea). - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New Patchy thread
- Original Message - From: "Phil Holmes" 4) try again? - Graham Soon. There you go. That seemed to work. I assume all I need to do is run patchy-staging daily? -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New Patchy thread
- Original Message - From: "Graham Percival" To: "Phil Holmes" Cc: "David Kastrup" ; Sent: Tuesday, January 31, 2012 12:42 PM Subject: Re: New Patchy thread On Tue, Jan 31, 2012 at 12:37:33PM -, Phil Holmes wrote: I assume I need to do something to update my git repo. However, it's vanilla and created using lily-git, so we would need instructions on how to do this anyway. Anyone know what's needed? I'll bet you a tenner that you used the OLD lily-git.tcl[1], which only gets a subset of the repository. [1] by "OLD", I unfortunately mean "the lily-git.tcl in the latest lilydev, so you're doing completely what we expect from a good and conscientious developer" [2]. [2] it would be really nice if lilydev 2.0 could come out soon. I did. AFAICS, the new lily-git isn't pushed as yet? Could you: 1) delete your current lilypond dir, then run: git clone git://git.sv.gnu.org/lilypond.git 2) put the resulting "lilypond" in the location you want, quite possibly renaming it to lilypond-git as well 3) change that repo so you have push access 4) try again? - Graham Soon. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New Patchy thread
On Tue, Jan 31, 2012 at 12:37:33PM -, Phil Holmes wrote: > I assume I need to do something to update my git repo. However, > it's vanilla and created using lily-git, so we would need > instructions on how to do this anyway. Anyone know what's needed? I'll bet you a tenner that you used the OLD lily-git.tcl[1], which only gets a subset of the repository. [1] by "OLD", I unfortunately mean "the lily-git.tcl in the latest lilydev, so you're doing completely what we expect from a good and conscientious developer" [2]. [2] it would be really nice if lilydev 2.0 could come out soon. Could you: 1) delete your current lilypond dir, then run: git clone git://git.sv.gnu.org/lilypond.git 2) put the resulting "lilypond" in the location you want, quite possibly renaming it to lilypond-git as well 3) change that repo so you have push access 4) try again? - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New Patchy thread
- Original Message - From: "Phil Holmes" To: "Graham Percival" Cc: "David Kastrup" ; Sent: Tuesday, January 31, 2012 12:29 PM Subject: Re: New Patchy thread - Original Message - From: "Graham Percival" To: "Phil Holmes" OK - so I really need to ensure that I can run lilypond-patchy-staging.py? Yes. It should be completely automatic and painless, once you have your ~/.lilypnod-patchy-config the way you like it. - Graham git successfully configured for push access (the CG is very good for this). Here goes. I get: terminal: python lilypond-patchy-staging.py Branch test-master-lock set up to track remote branch master from origin. fatal: Not a valid object name: 'origin/staging'. Message for you in /home/patchy/patchybuild/compile_results/log-2012-01-31-12.txt Deleted branch test-master-lock (was afb4c5f). logfile: Begin LilyPond compile, commit: afb4c5fb1766a317100887f62c72a660047c8892 *** FAILED STEP *** merge from staging maybe somebody pushed a commit directly to master? I assume I need to do something to update my git repo. However, it's vanilla and created using lily-git, so we would need instructions on how to do this anyway. Anyone know what's needed? -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New Patchy thread
- Original Message - From: "Graham Percival" To: "Phil Holmes" OK - so I really need to ensure that I can run lilypond-patchy-staging.py? Yes. It should be completely automatic and painless, once you have your ~/.lilypnod-patchy-config the way you like it. - Graham git successfully configured for push access (the CG is very good for this). Here goes. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New Patchy thread
On Tue, Jan 31, 2012 at 12:03:17PM -, Phil Holmes wrote: > - Original Message - From: "David Kastrup" > To: > Sent: Tuesday, January 31, 2012 11:55 AM > Subject: Re: New Patchy thread > > >"Phil Holmes" writes: > > > >>OK - I've now successfully run test-patches. It downloads and tests > >>the patch associated with issue 2263 (and tests clean). However, > >>there only appears to be a single patch in staging, and that's Carl's > >>fix for 2256. Any idea why it's testing 2263 instead? test-patches.py and lilypond-patchy-staging.py are completely different. > >>Also, FWIW, I've taken the email command out of config, and I now get > >>no notification of what has resulted, except what's shown on the > >>terminal. No "Message for you in...". take a look at the auto_compile_results_dir in your ~/.lilypond-patchy-config. Even without any mail command, you'll get the patchy log there. > >test-patches was not supposed to be on-topic yet... +1 although if people can get that working, that'd be great. I'll probably stop running test-patches.py myself on Feb 15. > >Wait. That answer does not fit the problem. I leave it in for > >reference, but the answer to your original question: test-patchy tests > >the last Rietveld review it can find on any issue being marked with > >"Patch-new" state. 2263 presumably is marked as such, 2256 apparently > >is something else, likely countdown or push. lilypond-patchy-staging.py does *nothing* with the code.google.com tracker. It strictly operates on git: git origin/staging and origin/master. > OK - so I really need to ensure that I can run > lilypond-patchy-staging.py? Yes. It should be completely automatic and painless, once you have your ~/.lilypnod-patchy-config the way you like it. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New Patchy thread
- Original Message - From: "David Kastrup" To: Sent: Tuesday, January 31, 2012 11:55 AM Subject: Re: New Patchy thread "Phil Holmes" writes: OK - I've now successfully run test-patches. It downloads and tests the patch associated with issue 2263 (and tests clean). However, there only appears to be a single patch in staging, and that's Carl's fix for 2256. Any idea why it's testing 2263 instead? Also, FWIW, I've taken the email command out of config, and I now get no notification of what has resulted, except what's shown on the terminal. No "Message for you in...". test-patches was not supposed to be on-topic yet... As opposed to the staging patchy which does all of its branch management itself and independent of the LILYPOND_GIT directory, the testing patchy _strictly_ work on whatever happens to be git's idea of the currently checked out material in LILYPOND_GIT. So you need to make sure that you have reset test-patches to the current master. Wait. That answer does not fit the problem. I leave it in for reference, but the answer to your original question: test-patchy tests the last Rietveld review it can find on any issue being marked with "Patch-new" state. 2263 presumably is marked as such, 2256 apparently is something else, likely countdown or push. -- David Kastrup OK - so I really need to ensure that I can run lilypond-patchy-staging.py? I'll have a go at that next, just once I've got a piece of actual music finished... -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New Patchy thread
"Phil Holmes" writes: > OK - I've now successfully run test-patches. It downloads and tests > the patch associated with issue 2263 (and tests clean). However, > there only appears to be a single patch in staging, and that's Carl's > fix for 2256. Any idea why it's testing 2263 instead? > > Also, FWIW, I've taken the email command out of config, and I now get > no notification of what has resulted, except what's shown on the > terminal. No "Message for you in...". test-patches was not supposed to be on-topic yet... As opposed to the staging patchy which does all of its branch management itself and independent of the LILYPOND_GIT directory, the testing patchy _strictly_ work on whatever happens to be git's idea of the currently checked out material in LILYPOND_GIT. So you need to make sure that you have reset test-patches to the current master. Wait. That answer does not fit the problem. I leave it in for reference, but the answer to your original question: test-patchy tests the last Rietveld review it can find on any issue being marked with "Patch-new" state. 2263 presumably is marked as such, 2256 apparently is something else, likely countdown or push. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New Patchy thread
hello, On 31 January 2012 11:39, Phil Holmes wrote: > OK - I've now successfully run test-patches. It downloads and tests the > patch associated with issue 2263 (and tests clean). However, there only > appears to be a single patch in staging, and that's Carl's fix for 2256. Any > idea why it's testing 2263 instead? Not sure why 'instead', but 2263 is the only current patch-new Tracker issue. Listed. http://code.google.com/p/lilypond/issues/list?can=2&q=Patch%3Dnew+&sort=patch&colspec=ID+Type+Status+Stars+Owner+Patch+Needs+Summary&x=type&cells=tiles -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
New Patchy thread
OK - I've now successfully run test-patches. It downloads and tests the patch associated with issue 2263 (and tests clean). However, there only appears to be a single patch in staging, and that's Carl's fix for 2256. Any idea why it's testing 2263 instead? Also, FWIW, I've taken the email command out of config, and I now get no notification of what has resulted, except what's shown on the terminal. No "Message for you in...". -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
