William Stein or I wrote: >>>> So sage-ptest may be responsible, somehow, for the faults that leave >>>> cores in apparently random directories and perhaps also for random test >>>> failures. >> >> Here's one problem: 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.) We could instead use >> >> .doctest_path_to_foo.py >> >> or >> >> .doctest_path_to_foo_ABC123.py >> >> where ABC123 is unique. With the latter we could run multiple >> simultaneous tests of the same file. I'll open a ticket or maybe use an >> existing one.
I've opened http://trac.sagemath.org/sage_trac/ticket/9739 specifically for this problem. > Could we use the tempfile module instead of using SAGE_TESTDIR. The > tempfile module makes files and directories by default that are unique > and are *designed* to live on a fast filesystem, which gets cleaned > regularly. > > sage: import tempfile Sure. I've added a comment about this to #9739. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
