Open Stack

On 10 July 2015 at 20:23, Kevin Benton <blak111 at gmail.com> wrote:
> How do we test to see what is failing in each project with the new version?

Look at any CI failure in the last 5 hours or so.

Or run tox :).

> Also, I'm responsible for the reference to the private mock method in
> Neutron. That particular reference is to prevent people from patching the
> same target twice because mock.patch.stopall() unwinds patches in a
> non-deterministic order in < py34 which leads to leftover monkey patches.
> These caused completely unrelated unit tests to randomly and inexplicably
> explode later. More details here:
> https://github.com/openstack/neutron/commit/1b60df85ba3ad442c2e4e7e52538e1b9a1bf9378

Thats fixed in 1.1.0. So you should be able to unwind that. If you
need a short term workaround, its in mock.mock now.

-Rob

-- 
Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Converged Cloud