I'm uncertain about the reasoning behind this bug. I'm afraid I haven't read all 248 comments above (!), but at #7 Steve Baker says "Look at the message that testtools builds for assertEquals fails."
But in a networking-calico test, if I force a failure, I see:
I'm uncertain about the reasoning behind this bug. I'm afraid I haven't read all 248 comments above (!), but at #7 Steve Baker says "Look at the message that testtools builds for assertEquals fails."
But in a networking-calico test, if I force a failure, I see:
AssertionError: {'/calico/ v1/config/ EndpointReporti ngEnabled' : True, '/calico/ v1/policy/ profile/ [truncated]... != {'/scalico/ v1/config/ InterfacePrefix ': 'tap', '/calico/ v1/policy/ profile/ opensta [truncated]... v1/Ready' : True, v1/config/ EndpointReporti ngEnabled' : True, v1/config/ InterfacePrefix ': 'tap', v1/policy/ profile/ openstack- sg-SGID- default/ rules': {u'inbound_rules': [{u'dst_ports': [u'1:65535'],
{'/calico/
'/calico/
- '/calico/
- '/calico/
? - - -
+ '/calico/ v1/policy/ profile/ openstack- sg-SGID- default/ rules': {'inbound_rules': [{'dst_ports': ['1:65535'],
- u'ip_version': 4,
...
And I don't see anything in that message that indicates which is the actual value and which is the expected.
So would appreciate if someone can clarify what is the justification for this bug.
Thanks - Neil