Opened 12 years ago
Last modified 11 years ago
#9739 closed defect
Handle duplicate file basenames when testing multiple files in parallel — at Version 1
Reported by: | mpatel | Owned by: | mvngu |
---|---|---|---|
Priority: | blocker | Milestone: | sage-4.7.2 |
Component: | doctest coverage | Keywords: | doctest scripts race condition unique filenames ptestlong -tp |
Cc: | drkirkby, jhpalmieri, leif, robertwb, jdemeyer | Merged in: | |
Authors: | Reviewers: | ||
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description (last modified by )
When we test
/path/to/foo.py
sage-doctest
writes
SAGE_TESTDIR/.doctest_foo.py
runs the new file through python
, and deletes it. This can cause
collisions when we test in parallel multiple files with the same
basename, e.g., __init__
, all
, misc
, conf
, constructor
, morphism
, index
, tests
, homset
, element
, twist
, tutorial
, sagetex
, crystals
, cartesian_product
, template
, ring
, etc.
There's a similar problem with testing non-library files, which sage-doctest
first effectively copies to SAGE_TESTDIR
.
See sage-devel for background.
This ticket may help with some of the doctesting problems discussed on the Sage mailing lists. Related tickets: #9224, #9225, #9449.
Change History (2)
comment:1 Changed 12 years ago by
- Description modified (diff)
Changed 12 years ago by
Frequency-sorted list of doctest file basenames (includes .py, .pyx, .pxi, .rst, .tex files). Not a patch.
William Stein suggests: