11273cfe53
Opportunistic db test cases create schemas on demand, so that each test case which inherits the base test case class, will get its own db schema (i. e. races between tests are not possible). In order to do schema provisioning we have to connect to RDBMS server first. So far we've been connecting to the openstack_citest database, which is guaranteed to exist on CI nodes. It turns out, there are a few test cases in Nova (maybe in other projects as well), that drop and recreate the openstack_citest database. If they happen to do that when the opportunistic db fixture is in the middle of provisioning a schema, those tests will fail (as there is an an open session to the database and thus it can't be dropped). This can be solved easily by changing the way we provision new schemas in opportunistic db test cases as actually, we don't have to connect to the openstack_citest database at all: - for MySQL we can use an empty db name to connect to MySQL server, but not to a particular database - PostgreSQL requires us to specify the database name. We can use the service postgres database here (PostgreSQL shell utils such as createdb, createuser, etc use it for the very same reason) Closes-Bug: #1328997 Change-Id: Id82090743e8b93f6c960de066fd05d8a2f9fb934 |
||
|---|---|---|
| doc/source | ||
| etc | ||
| openstack | ||
| pypi | ||
| tests | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .testr.conf | ||
| HACKING.rst | ||
| LICENSE | ||
| MAINTAINERS | ||
| MANIFEST.in | ||
| README.rst | ||
| TESTING.rst | ||
| obsolete.txt | ||
| requirements-py3.txt | ||
| requirements.txt | ||
| run_tests.sh | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements-py3.txt | ||
| test-requirements.txt | ||
| tox.ini | ||
| update.py | ||
| update.sh | ||
README.rst
The Oslo Incubator
The Oslo program produces a set of python libraries containing infrastructure code shared by OpenStack projects. The APIs provided by these libraries should be high quality, stable, consistent and generally useful.
The process of developing a new Oslo API usually begins by taking code which is common to some OpenStack projects and moving it into this repository. Incubation shouldn't be seen as a long term option for any API - it is merely a stepping stone to inclusion into a published Oslo library.
For more information, see our wiki page:
Running Tests
To run tests in virtualenvs (preferred):
sudo pip install tox
toxTo run tests in the current environment:
sudo pip install -r requirements.txt
nosetestsTo run tests using MySQL or PostgreSQL as a DB backend do:
OS_TEST_DBAPI_ADMIN_CONNECTION=mysql://user:password@host/database tox -e py27Note, that your DB user must have permissions to create and drop databases.