#12486: Add patchbot to Sage itself.
----------------------------------------------+-----------------------------
Reporter: robertwb | Owner: mvngu
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.1
Component: doctest | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Robert Bradshaw, Dan Drake | Merged in:
Dependencies: | Stopgaps:
----------------------------------------------+-----------------------------
Comment (by robertwb):
The patchbot deletes tickets directories when they are closed. It might be
worth having an option to delete them after every run, but then a full re-
clone and re-build would be required to test any additional patches
(expensive).
As for space, all the build and .c files are hard linked from sage-main
(unless they're changed), so the aggregate use of the directories is about
100MB each ticket (not each run). Even if we got up to, say, 500 open
tickets you are looking at a stead state of 50GB total, not per day.
It will only apply patches to the sage-main tree, which it re-clones for
every ticket, but the doctests and code itself could do anything, so one
can't rule out any global state (though if there it's both strange and a
bug).
I'm all in favor of getting this in and iterating on it there. I made some
minor changes and will try to refresh these patches shortly.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12486#comment:23>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
