Hi Ross, On Wed, Feb 3, 2010 at 8:50 AM, Minh Nguyen <[email protected]> wrote:
<SNIP> > The thrust of this post is how do I use sage -tp properly... See the Developers' Guide, especially the sections "Parallel testing many modules" [1] and "Parallel testing the whole Sage library" [2]. > Id like to do the equivalent to sage -testall using sage -tp > Is the equivalent command sage -long -optional? Not quite. The option "-testall" is equivalent to doctesting the whole Sage library and standard documentation using "-t". So if you want to do ./sage -testall you could issue the following equivalent command: ./sage -t devel/sage-main/ You can think of them as synonymous with each other. The incantation "./sage -testall" is much shorter than explicitly specifying the the main branch of your Sage installation. > How do I do ALL the tests using -tp and if I have say a 4 core machine > what options do I pass to -tp If you want to use 4 threads for parallel doctesting, you could do ./sage -tp 4 devel/sage-main/ or replace devel/sage-main/ with the directory to you want to perform parallel doctest on. For example, the command ./sage -tp 4 devel/sage-main/sage only performs parallel doctest on the whole Sage library. See the chapter "Parallel Testing the Sage Library" [3] of the Developers' Guide for more information. > In particular, how do I work out how many threads to use? On a multiuser system such as a machine within the Sage cluster, I often use about a quarter of the total number of cores on that machine. This allows other developers to run parallel build/doctests. The number of threads to use for parallel doctesting depends on your machine (and how nice you want to be :-). > Finally if I re-run the tests that fail in parallel but pass > "non-parallel" (as mentioned in included email below), should I > consider them as passed or report them? Please report such situations. > Despite the multiple questions, Im really just asking, how do I use > sage -tp properly... The Developers' Guide has a chapter on parallel doctesting. In any case, don't hesitate to ask if it doesn't make sense or lacks clarification. [1] http://www.sagemath.org/doc/developer/doctesting.html#parallel-testing-many-modules [2] http://www.sagemath.org/doc/developer/doctesting.html#parallel-testing-the-whole-sage-library [3] http://www.sagemath.org/doc/developer/doctesting.html -- Regards Minh Van Nguyen -- 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-support URL: http://www.sagemath.org
