#9967: Allow concurrent running/testing of multiple sage branches
---------------------------------------+------------------------------------
Reporter: robertwb | Owner: ddrake
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.6
Component: doctest | Keywords:
Author: Robert Bradshaw | Upstream: N/A
Reviewer: Dan Drake, John Cremona | Merged:
Work_issues: |
---------------------------------------+------------------------------------
Changes (by robertwb):
* status: needs_work => needs_review
Comment:
Replying to [comment:19 ddrake]:
> Another question: how does one rebuild a non-default branch? Let's say I
have a session running in the main branch, and on the side, I'm doing
some testing in the "test" branch. I want to rebuild in sage-test, but I
don't want to switch the symlink, because then the running session will
get confused.
>
> All of the various "-b" options say that they switch to a branch -- do
we have to do that?
Ideally we would support building stuff in parallel too, but that was
beyond the scope of this ticket. The makefile is a bit trickier, as it
creates the list before SAGE_BRANCH gets set. I think all the different
testing entry points should be consolidated, probably into "sage
-testeall" which could take various options.
> Maybe another way to say this: I want at least one of these statements
to be true:
>
> * "a running session / set of doctests / etc will never get confused
if the symlink gets switched around"
This should be true. On starting sage, SAGE_BRANCH gets set right away if
it wasn't set before, so you shouldn't confuse a running/testing sage by
swapping the symlink out from under it. (All sub-proceses will inherit the
environment variable.)
> * "you can rebuild a branch with something like {{{env SAGE_BRANCH=foo
./sage -b}}}"
>
> Does this seem reasonable?
I'd like both to be true, but at the moment the first is, which I think is
the most valuable first step. OK, I've made a fix to sage-maketest. Note
that SAGE_BRANCH will always be set at this point (whether by the user or
by sage-env). Is there anything else that needs work on this?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9967#comment:21>
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.
