On Fri, Feb 10, 2012 at 12:17 PM, D. S. McNeil <dsm...@gmail.com> wrote: > On Fri, Feb 10, 2012 at 4:27 AM, Robert Bradshaw > <rober...@math.washington.edu> wrote: >> It's easy. >> >> 1) Download and build a pristine copy of Sage for testing. >> 2) Apply http://trac.sagemath.org/sage_trac/ticket/12486 to the >> sage-scripts directory. >> 3) Run sage --patchbot > > There are maybe two tweaks to these directions I'd suggest: > > (2a) I wasn't sure what the sage-scripts directory was; there's > nothing by that name in my 4.8. There's a sage_scripts spkg but it > seems to put a lot of stuff in local/bin, which seems to work.
Yep. > (2b) To avoid a "Permission denied" error when running sage > --patchbot, you have to make patchbot.py executable. > > The second one's obvious, the first one took me a few minutes to find > the right directory.. D'oh, hg export doesn't preserve the permission bit by default. Ironically, both of these points are very relevant to the recent "log messages" thread. On Fri, Feb 10, 2012 at 12:16 PM, kcrisman <kcris...@gmail.com> wrote: > Thanks so much for the answers to all this, Robert. > >> > What are the resource requirements on something like this? For >> > example, >> >> > * How many free MB should be always available? >> >> Whatever it takes to build/test Sage these days for RAM, plus disk >> space for a single Sage install + 100MB/ticket disk. > > Hmm, 100MB per ticket is actually nontrivial on older machines. True, though for modern hardware, this comes out to about $0.01/ticket. >> > * Does this distributed patchbot always delete the patches when it's >> > done? >> >> It keeps them around until the ticket is closed. It could be worth >> making this configurable. > > For sure on older machines. > >> > * Can one stop the patchbot if one wants to do something else on the >> > computer without ill effect? >> >> Yes. The ticket will be marked as "pending" for the next 12 hours or >> so if you never report any results, but that's the only ill effect. >> You can also specify hours of the day that you want it to run, e.g. >> "22-7,10-16" for 10pm-7am, 10am-4pm. Day of week could be valuable as >> well. > > I would have *never* guessed this from the patch! I finally found > where this happens. Maybe you could post a "sample" conf file to the > ticket as well using all the options; that would be a middle ground > between the current patch and full docs. See line 360+ of patchbot.py for the "default" config file. I'll try to answer any other questions anyone has as well which should also help fill the gap. > On a more personal note, I am always amazed by the programming ability > and motivation of some of the core developers, naturally including > yourself and all the things you've contributed over the years. > Jeroen's release script and Jason's work on the notebook/Sagecell come > to mind too. I can only watch in admiration - way to go! Thanks! > Is the "get a whole lot busier" due to child # x, for some x>2? Yep, numbers 3 and 4. Any day now... - Robert -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
