Many functional tests don't call stop_servers after start_servers
Bug #1043416 reported by
Vincent Untz
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Medium
|
Vincent Untz |
Bug Description
I see many tests in the functional tests that don't call stop_servers at the end, after a call to start_servers at the beginning. test_index_
I don't know if this is intended or not (clearly, not having to restart the servers is a speed win). However, one net result I can see here is that I do have some processes from the test around after the tests have been run. And that is bad.
So should all tests calling start_servers() also call stop_servers()? Or should we have a way to automatically stop the servers?
Changed in glance: | |
milestone: | none → folsom-rc1 |
status: | Fix Committed → Fix Released |
Changed in glance: | |
importance: | Undecided → Medium |
Changed in glance: | |
milestone: | folsom-rc1 → 2012.2 |
To post a comment you must log in.
We should absolutely be calling stop_servers explicitly