#7079: [with patch, needs review] parallel doctest broken in Sage 4.1.2.alpha4
if
HOME/.sage/tmp doesn't exist
----------------------+-----------------------------------------------------
Reporter: mvngu | Owner: tbd
Type: defect | Status: new
Priority: critical | Milestone: sage-4.1.3
Component: doctest | Keywords:
Reviewer: | Author:
Merged: |
----------------------+-----------------------------------------------------
Comment(by jhpalmieri):
I think the patch is a good idea. It basically works for me on Mac OS X
10.5 and on sage.math. Maybe it should get a positive review and then we
should work on the "mysterious" errors. On sage.math, if I don't apply the
patch, delete my .sage directory, and do parallel doctesting, it's a
complete disaster. Once I apply the patch, if I delete my .sage
directory, and while in SAGE_ROOT I do {{{sage -tp 2
devel/sage/sage/algebras}}}, then I get
{{{
init.sage does not exist ... creating
touch: cannot touch `/home/palmieri/.sage//init.sage': No such file or
directory
Global iterations: 1
File iterations: 1
No cached timings exist; will create upon successful finish.
Doctesting 21 files doing 2 jobs in parallel
sage -t devel/sage/sage/algebras/free_algebra_quotient.py
A mysterious error (perhaps a memory error?) occurred, which may have
crashed doctest.
}}}
and then all of the other doctests pass. This is not related, I think, to
the problems on Mac OS X 10.6: if I do it again (but with an existing
.sage directory), all tests pass. Maybe the issue is that one thread is
running a doctest while another is still busy creating .sage and all of
its subdirectories, and so the doctest crashes? Or two threads are both
trying to create .sage at the same time, and this leads to problems? This
might also explain mvngu's problems with .sage/valgrind. Should we run
one test and then switch to parallel testing, or should we run the script
(whatever it is) that creates .sage, and then go on to parallel testing?
So I don't know if this should get a positive review and the mysterious
crashes should be in a separate ticket, since that would solve most of the
problem, or if this should be marked "needs work" and the whole thing
fixed at once...
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7079#comment:8>
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
-~----------~----~----~----~------~----~------~--~---
