yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #56659
[Bug 1259292] Re: Some tests use assertEqual(observed, expected) , the argument order is wrong
Reviewed: https://review.openstack.org/338179
Committed: https://git.openstack.org/cgit/openstack/networking-calico/commit/?id=8599fe0af907bc5aeff29c994bafdf87ef558b71
Submitter: Jenkins
Branch: master
commit 8599fe0af907bc5aeff29c994bafdf87ef558b71
Author: SongmingYan <yan.songming@xxxxxxxxxx>
Date: Wed Jul 6 06:48:10 2016 -0400
Fix order of arguments in assertEqual
Some tests used incorrect order assertEqual(observed, expected).
The correct order expected by testtools is
assertEqual(expected, observed).
Closes bug: #1259292
Change-Id: I39aa28bea07a3cc6dcab472d526b7d3436d5270d
** Changed in: networking-calico
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 Bandit:
In Progress
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:
Fix Released
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:
Fix Released
Status in PBR:
Fix Released
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:
In Progress
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