#10326: Various clean-up in local/bin/sage-sage
---------------------------------------------------+------------------------
Reporter: jdemeyer | Owner: jason
Type: enhancement | Status: closed
Priority: minor | Milestone: sage-4.6.1
Component: misc | Resolution: fixed
Keywords: scripts sage-sage usage help messages | Author: Jeroen
Demeyer
Upstream: N/A | Reviewer: Rob
Beezer, Leif Leonhardy
Merged: sage-4.6.1.alpha3 | Work_issues:
---------------------------------------------------+------------------------
Comment(by leif):
Replying to [comment:15 rbeezer]:
> OK, I'll bite and be ''someone''. See #10429 for a link back to comment
9 above with Leif's suggestions.
Thanks, ''someone''... ;-)
[[BR]]
> While I have your attention here on-topic - is it possible to do
-testall in combination with something like -tp 4 ? I'm always looking
to do this when reviewing. I can't see from the code that it is possible.
`sage -testall` currently doesn't support multiple threads, since there's
no separate option to specify the number, just the combined option `-tp`,
which excludes `-testall`.
But you could (from `SAGE_ROOT`) run `make ptest NUM_THREADS=4` ('''not'''
`ptestall`, which includes `--optional`), which is perhaps less convenient
since you have to `cd` to `SAGE_ROOT`, or use `make`'s `-C` option (`make
-C $SAGE_ROOT ...`). Alternatively, do
{{{
#!sh
$ export NUM_THREADS=4 # once per session, or in your ~/.bashrc
$ make -e ptest # from SAGE_ROOT; '-e' tells 'make' to take
NUM_THREADS
# from your environment, i.e. override the
default setting(s)
}}}
Also, the `make` method doesn't include testing the examples as `sage
-testall` (in theory) does, but ''fortunately^TM^'' that isn't implemented
at all yet. (`SAGE_ROOT/examples/test_all`, which is also called when you
run `sage -testall`, just issues a warning and exits.) :)
> Let me know, and I'll propose it on a ticket if it is not currently
possible. Thanks. -Rob
Feel free to open a ticket for that, suggesting some suitable option to
add. (`-p <NUM>`, `--threads=<NUM>`, or `-j<NUM>` like `make` takes? Note
that `make -j4 ptest` wouldn't work as one perhaps would expect.)
Or we could simply implement `sage -tp <NUM> --all`, `sage -ptestall
<NUM>`, `sage -tp-all <NUM>` or whatever. Separating the option to specify
the number of threads (and the "all" option) is IMHO a better choice.
We're going to merge the scripts for sequential and parallel testing
anyway.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10326#comment:17>
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.