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. > > * 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. -- 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
