#9739: Handle duplicate file basenames when testing multiple files in parallel
-------------------------------+--------------------------------------------
   Reporter:  mpatel           |          Owner:  mvngu          
       Type:  defect           |         Status:  needs_work     
   Priority:  critical         |      Milestone:  sage-4.7.1     
  Component:  doctest          |       Keywords:  doctest scripts
Work_issues:                   |       Upstream:  N/A            
   Reviewer:  Robert Bradshaw  |         Author:  Mitesh Patel   
     Merged:                   |   Dependencies:                 
-------------------------------+--------------------------------------------

Comment(by jhpalmieri):

 Replying to [comment:52 leif]:

 > > By the way, using the PID in the directory name means creating many
 directories: as far as I can tell, running `sage -t DIR` uses a different
 process for each file in DIR.  Perhaps the PID should be in the mangled
 filename instead of part of a new directory.
 >
 > At least at the moment, we're dealing with `ptest*` only here, so that's
 another matter (if you want to run multiple `testlong`s for example using
 the same temporary directory). So `sage -t ...` wouldn't create any
 directories at all.

 I was envisioning patching sage-doctest, since that's what copies the file
 being tested to SAGE_TESTDIR (and later deletes it), and it gets run by
 "sage -t ...", "sage -tp ...", etc.   Running "sage -tp DIR" also uses a
 different PID for each execution of sage-doctest.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9739#comment:53>
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.

Reply via email to