#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 davidloeffler):
My experience with running patchbot has been that many tickets (notably
those that add new modules to the reference manual) do seem to pollute the
global state, particularly for documentation building purposes, where the
docbuild log for running patchbot on ticket X will start complaining that
it can't find a file that is added in some other ticket Y that it
previously tested. (I think this is because the {{{sage-clone}}} script
hard-links the Sphinx environment pickle.)
Moreover, even without "cross-branch contamination", adding source files
and then removing them tends to leave junk in the Sage build tree. Thus
the patchbot isn't really doing its job properly, of simulating the effect
of applying the latest set of patches to a clean copy of Sage. So I found
it preferable to fiddle with the patchbot {{{test_a_ticket}}} code such
that it always made a new branch, then deleted it afterwards.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12486#comment:27>
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.
