yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #49403
[Bug 1259292] Re: Some tests use assertEqual(observed, expected) , the argument order is wrong
** Changed in: congress
Milestone: None => mitaka
** Changed in: congress
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1259292
Title:
Some tests use assertEqual(observed, expected) , the argument order is
wrong
Status in Barbican:
In Progress
Status in Ceilometer:
Invalid
Status in Cinder:
Fix Released
Status in congress:
Fix Released
Status in Designate:
Fix Released
Status in Glance:
Fix Released
Status in heat:
Fix Released
Status in OpenStack Dashboard (Horizon):
In Progress
Status in OpenStack Identity (keystone):
Fix Released
Status in Magnum:
Fix Released
Status in Manila:
Fix Released
Status in Mistral:
Fix Released
Status in Murano:
Fix Released
Status in OpenStack Compute (nova):
Won't Fix
Status in python-ceilometerclient:
Invalid
Status in python-cinderclient:
Fix Released
Status in python-designateclient:
Fix Committed
Status in python-mistralclient:
Fix Released
Status in python-solumclient:
Fix Released
Status in Python client library for Zaqar:
Fix Released
Status in Sahara:
Fix Released
Status in zaqar:
Fix Released
Bug description:
The test cases will produce a confusing error message if the tests
ever fail, so this is worth fixing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/barbican/+bug/1259292/+subscriptions