Actions
Bug #17266
closedvirtualenv default paths not uniquely named
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
build
Target version:
-
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
virtualenvs are used in the build for testing the various python projects. They're created, by default, in /tmp/<tool>-virtualenv. This means they collide when two builds happen on one host (shared build machine, multiple repos, whatever).
There doesn't seem to be any good reason not to use mktemp or something like it and completely avoid the possibility of collision.
Actions