Volume tests depend on logging for "tests"
Bug #932137 reported by
Jason Kölker
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Low
|
Rongze Zhu | ||
OpenStack Compute (nova) |
Fix Released
|
Low
|
Rongze Zhu |
Bug Description
nova.tests.
Changed in cinder: | |
importance: | Undecided → Low |
Changed in cinder: | |
milestone: | none → folsom-rc1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | none → folsom-rc1 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | folsom-rc1 → 2012.2 |
Changed in nova: | |
milestone: | folsom-rc1 → 2012.2 |
To post a comment you must log in.
Ok, usage of this stream seems to be limited to the check_for_export() tests and should be easy to cleanup.
check_for_export() raises an exception if there's a problem and it does nothing if it succeeds
The tests should just check whether an exception was raised
For reference, this test code was introduced by this series of commits: 144fa50..0dcd680