> It seems that the temporary path is not transcient: it's the very same
> path across multiple test sessions... Maybe a bad use of mkstemp() or
> the like?
Ok, something weird:
The temporary env path is created as:
env_path = os.path.join(tempfile.gettempdir(), 'trac-tempenv')
which means that it's not possible to run more than one test session
at once on the same machine, as the temporary directory is the very
same for all instances.
Moreover, when the temporary directory already exists, many setUp()
TestCase methods fail to execute.
When setUp() aborts, tearDown() is never called by the Python unittest
framework, and the existing directory is never cleared up. This issue
makes any subsequent test session to fail as well.
I would suggest that the temporary directory is unique for a single
test session, which would solve the first issue and reduce the
occurrences of the second one.
Cheers,
Manu
--
You received this message because you are subscribed to the Google Groups "Trac
Development" 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/trac-dev?hl=en.
