Hi,
Le 09/05/2016 16:38, Amrith Kumar a écrit :
So I’m able to run the py34 tests in about 10s if I run the dangling
mock detector with a depth of 0 or 1.
IMHO the strange mock detector code must be removed. It is very slow and
I don't understand its purpose.
The mock module has a nice stop_all() method, why not using it?
https://docs.python.org/dev/library/unittest.mock.html#unittest.mock.patch.stopall
The fixtures and oslotest modules also help to stop mocks.
(I don't know if the "mock detector" thing is related to the slow tests
on Python 3.)
Victor
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
