Ivan A. Melnikov 79d9e12ed6 Use addCleanup instead of tearDown in test_sql_persistence ...

TestCase.tearDown() is not called if setUp raises exception,
but we have to close backend and release lock before executing
other tests. The easiest way to do it is to use addCleanup
instead of tearDown for freeing resources.

Change-Id: I885bb7d491f4b3ee06a351f5d22087e23804e19b

2014-01-28 15:01:39 +04:00

..

engines

Doc strings and comments clean-up

2014-01-26 23:08:39 +02:00

examples

Doc strings and comments clean-up

2014-01-26 23:08:39 +02:00

jobs

Doc strings and comments clean-up

2014-01-26 23:08:39 +02:00

listeners

Doc strings and comments clean-up

2014-01-26 23:08:39 +02:00

openstack

Update oslo-incubator copy to oslo-incubator commit 8b2b0b743

2013-12-21 11:28:31 -08:00

patterns

Doc strings and comments clean-up

2014-01-26 23:08:39 +02:00

persistence

Doc strings and comments clean-up

2014-01-26 23:08:39 +02:00

tests

Use addCleanup instead of tearDown in test_sql_persistence

2014-01-28 15:01:39 +04:00

utils

Merge "Test using mysql + postgres if available"

2014-01-27 09:52:45 +00:00

__init__.py

Continue on getting ready for the memory impl. to be useful.

2013-05-12 14:45:24 -07:00

atom.py

Doc strings and comments clean-up

2014-01-26 23:08:39 +02:00

exceptions.py

Doc strings and comments clean-up

2014-01-26 23:08:39 +02:00

flow.py

Doc strings and comments clean-up

2014-01-26 23:08:39 +02:00

states.py

Doc strings and comments clean-up

2014-01-26 23:08:39 +02:00

storage.py

Doc strings and comments clean-up

2014-01-26 23:08:39 +02:00

task.py

Update execute/revert comments

2014-01-26 21:30:26 -08:00

test.py

Capture task duration

2013-12-09 10:58:03 -08:00

version.py

Prepare for 0.1 release

2013-10-14 01:03:32 +00:00