On Fri, Feb 10, 2012 at 10:55 AM, kcrisman <[email protected]> wrote: > > > On Feb 10, 4:27 am, Robert Bradshaw <[email protected]> > wrote: >> It's easy. >> >> 1) Download and build a pristine copy of Sage for testing. >> 2) Applyhttp://trac.sagemath.org/sage_trac/ticket/12486to the >> sage-scripts directory. >> 3) Run sage --patchbot >> >> Everyone's results will be consolidated athttp://patchbot.sagemath.org/. >> Hopefully this will allow us to get >> results from wide variety of architectures, platforms, and versions. > > 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. > * 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. > * 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. > * What kind of network authorization would be needed? You need to be able to connect to http://patchbot.sagemath.org and http://trac.sagemath.org/ > * Firewalls? > * Etc. Nothing else really, though some precaution should be taken as you're building and running arbitrary code (by default from people with a trac account and a previously accepted patch, though you can customize this as well). > Some stuff seems less than 100% doctested as well :) Yeah, there's lots of room for improvement, but waiting around until I have time to add everything I'd like to hasn't worked out the last 6 months, and my life is about to get a whole lot busier, so it's time to get this out and let other people use and contribute too. > But it's a great idea, if this is as easy as doing sage --patchbot and > letting it run over a weekend. Yep, that's the goal. - Robert -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
