ZaqarEventSinkTest is too strict

Bug #1549264 reported by Thomas Herve on 2016-02-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
High
Thomas Herve

Bug Description

In recent build:

2016-02-24 11:13:10.511 | 2016-02-24 11:13:10.487 | testtools.matchers._impl.MismatchError: !=:
2016-02-24 11:13:10.517 | 2016-02-24 11:13:10.493 | reference = ['IN_PROGRESS', 'IN_PROGRESS', 'COMPLETE', 'COMPLETE']
2016-02-24 11:13:10.524 | 2016-02-24 11:13:10.500 | actual = [u'IN_PROGRESS', u'COMPLETE', u'IN_PROGRESS', u'COMPLETE']

There is no need to check ordering.

Fix proposed to branch: master
Review: https://review.openstack.org/284100

Changed in heat:
status: New → In Progress

Reviewed: https://review.openstack.org/284100
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=fe511a958c1f9e95ae4af8588896f293d7627e71
Submitter: Jenkins
Branch: master

commit fe511a958c1f9e95ae4af8588896f293d7627e71
Author: Thomas Herve <email address hidden>
Date: Wed Feb 24 13:08:06 2016 +0100

    Make ZaqarEventSinkTest more lenient

    We don't have strong ordering of events enforced, so there is no need to
    test that events arrive in order, and it actually make tests fail
    intermittently. Let's relax that check.

    Change-Id: I73be763df5ddf863e29df1b9ac8792f05700e006
    Closes-Bug: #1549264

Changed in heat:
status: In Progress → Fix Released

This issue was fixed in the openstack/heat 6.0.0.0b3 development milestone.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers