Tox exhausting /tmp partition
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Jamie Lennox |
Bug Description
So every time i tried to run tox i was getting the error message that /tmp was out of space when trying to create the virtual env which means that creating the virtualenv was filling a 3gb partition.
In our tox requirements we currently have:
deps = -r{toxinidir}
.[ldap]
.[memcache]
.[mongodb]
By having each of those additional dependencies listed as .[XXX] tox is installing . (the keystone working directory) into a virtualenv then determining the entry point. This created 3 seperate /tmp/pip-XXX-build directories. The other side of this is that my keystone/
There are two fixes to this:
1. reset my .testrepository database
2. dependencies should be listed together like .[XXX,YYY,ZZZ] so . is only copied once
As an addition to this because we are installing dependencies with .[XXX] which means install . (working directory/keystone) + XXX dependencies there is no reason to specifically install -r requirements.txt as this will be handled for us.
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | liberty-rc1 → 8.0.0 |
Fix proposed to branch: master /review. openstack. org/218693
Review: https:/