#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 drkirkby):
Replying to [comment:20 leif]:
> Replying to [comment:19 drkirkby]:
> > There is another problem, which could exist even if every file had a
different name.
> >
> > If one tests multiple instances of Sage serially, then since they both
write to $HOME/.sage, failures can occur even if the file names of the
doctests are unique to any one copy of Sage.
>
> Well this would definitely be a '''user error'''. You can always set
`DOT_SAGE` or `SAGE_TESTDIR` (or whatever it is called) if you want to run
multiple tests simultaneously in different shells, even in / with the
''same'' Sage installation.
>
> > They need to be unique for any number of instances of Sage. I think
testing under $HOME/.sage is a bit silly myself - it would be better to
test under the directory where Sage is installed.
>
> Definitely not, since this wouldn't work for site installations, where
users usually have no write permissions under `SAGE_ROOT`.
>
>
> > I don't know if this patch can handle that situation, but it would be
good if it could.
>
> One could use Sage's PID, user and machine parameters etc. to try to
create unique directories, or generally create "random" directories with
`mktemp (1)` or `mkdtemp()`, but I think this would be an overkill, since
the user can itself do such by setting one of the above variables.
I disagree. I don't think creating unique temporary files is overkill. 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.
Dave
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9739#comment:21>
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.
