#9739: Handle duplicate file basenames when testing multiple files in parallel
-------------------------------+--------------------------------------------
Reporter: mpatel | Owner: mvngu
Type: defect | Status: needs_work
Priority: blocker | Milestone: sage-4.6.1
Component: doctest | Keywords: doctest scripts
Author: Mitesh Patel | Upstream: N/A
Reviewer: Robert Bradshaw | Merged:
Work_issues: |
-------------------------------+--------------------------------------------
Comment(by leif):
Replying to [comment:21 drkirkby]:
> I disagree. I don't think creating unique temporary files is overkill.
I didn't say that, but it IMHO suffices to have unique names in the
namespace of a ptest run.
> It would be far less error prone. With a test you want to run many
times, having a dozen copies of Sage around for test purposes is quite a
sensible thing to do with multi-core machines. Havving to set DOT_SAGE for
each is annoying, when a unique temporary file could be made.
As I said, you can automatically set up unique test directories by setting
one of the above variables e.g. based on the "login" shell's PID, one per
terminal / shell.
If multiple machines share the same filesystem, simply add e.g. the
hostname, too.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9739#comment:22>
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.