Hi folks, The following forwarded message is from someone who wasn't able to directly send to this list.
-- Regards Minh Van Nguyen ---------- Forwarded message ---------- From: ross k <[email protected]> Date: Wed, Feb 3, 2010 at 8:40 AM Subject: Fwd: using sage -tp vs testall To: Minh Nguyen <[email protected]> Minh Sorry to send this to you directly. Tried sending this to sage-devel but I think I need to request membership before I can post there all the best Ross ---------- Forwarded message ---------- From: ross k <[email protected]> Date: Wed, Feb 3, 2010 at 7:50 AM Subject: using sage -tp vs testall To: [email protected] Hi The thrust of this post is how do I use sage -tp properly... I just got access to a new machine (Not sure at the moment but its either 4 or 8 core). Id like to do the equivalent to sage -testall using sage -tp Is the equivalent command sage -long -optional? (When I looked at sage -advanced, in the description of "-testall", theres mention of testing examples as well, but not in the description of "-tp") 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 In particular, how do I work out how many threads to use? 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? Despite the multiple questions, Im really just asking, how do I use sage -tp properly... Hope this makes sense and was the right forum Ross > Hi Alex, > > On Mon, Feb 1, 2010 at 11:54 PM, Alex Ghitza <[email protected]> wrote: > > <SNIP> > > > The following tests failed: > > sage -t -long devel/sage/sage/parallel/decorate.py # Segfault > > > > This only seems to happen when I run the whole testsuite. If I try to > > run this test on its own, it always passes. (I had the same issue in > > alpha0.) It could just be something that only comes up under stress -- > > I was testing things in parallel with 16 threads. Anyway, I don't > > think we can do much about it right now. > > The above failure often comes up when performing parallel doctests on > mod.math. I have seen it many times during the Sage 4.3.2 release > milestone. However, when it is run by itself, not part of a parallel > doctest of the whole Sage library, it would pass. Sometimes it would > also pass during a parallel doctest on mod.math. > -- > 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
