On Tue, Jan 31, 2012 at 12:03:17PM -0000, Phil Holmes wrote: > ----- Original Message ----- From: "David Kastrup" <d...@gnu.org> > To: <lilypond-devel@gnu.org> > Sent: Tuesday, January 31, 2012 11:55 AM > Subject: Re: New Patchy thread > > >"Phil Holmes" <em...@philholmes.net> 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
