yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #53600
[Bug 1259292] Re: Some tests use assertEqual(observed, expected) , the argument order is wrong
Reviewed: https://review.openstack.org/338001
Committed: https://git.openstack.org/cgit/openstack/solum/commit/?id=adc1b9ddcc77d7f8bc1c05c830f7b0c4a0805b8a
Submitter: Jenkins
Branch: master
commit adc1b9ddcc77d7f8bc1c05c830f7b0c4a0805b8a
Author: yuyafei <yu.yafei@xxxxxxxxxx>
Date: Wed Jul 6 15:32:06 2016 +0800
Fix argument order for assertEqual to (expected, observed)
assertEqual expects that the arguments provided to it should be
(expected, observed). If a particluar order is kept as a convention,
then it helps to provide a cleaner message to the developer if Unit
Tests fail. The following patch fixes this issue.
TrivialFix
Closes-Bug: #1259292
Change-Id: I608b07f857d9fa2d401cab35fff6bdf2defa6d55
** Changed in: solum
Status: In Progress => 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 Astara:
Fix Released
Status in Barbican:
In Progress
Status in Blazar:
New
Status in Ceilometer:
Invalid
Status in Cinder:
Fix Released
Status in congress:
Fix Released
Status in daisycloud-core:
New
Status in Designate:
Fix Released
Status in Freezer:
In Progress
Status in Glance:
Fix Released
Status in glance_store:
Fix Released
Status in Higgins:
New
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 networking-calico:
New
Status in networking-infoblox:
In Progress
Status in networking-l2gw:
In Progress
Status in networking-sfc:
Fix Released
Status in OpenStack Compute (nova):
Won't Fix
Status in os-brick:
In Progress
Status in PBR:
New
Status in pycadf:
New
Status in python-barbicanclient:
In Progress
Status in python-ceilometerclient:
Invalid
Status in python-cinderclient:
Fix Released
Status in python-designateclient:
Fix Committed
Status in python-glanceclient:
Fix Released
Status in python-mistralclient:
Fix Released
Status in python-solumclient:
Fix Released
Status in Python client library for Zaqar:
Fix Released
Status in Rally:
New
Status in Sahara:
Fix Released
Status in Solum:
Fix Released
Status in sqlalchemy-migrate:
New
Status in SWIFT:
New
Status in tacker:
In Progress
Status in tempest:
Invalid
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/astara/+bug/1259292/+subscriptions