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? * Does this distributed patchbot always delete the patches when it's done? * Can one stop the patchbot if one wants to do something else on the computer without ill effect? * What kind of network authorization would be needed? * Firewalls? * Etc. Some stuff seems less than 100% doctested as well :) But it's a great idea, if this is as easy as doing sage --patchbot and letting it run over a weekend. -- 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
