[openstack-dev] [trove] timeouts in gate-trove-python34-db

Amrith Kumar amrith at tesora.com
Mon May 9 14:38:49 UTC 2016

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.

I'd also like to figure out how we can get the py34 tests to show progress like py27 does. If a test fails, it is much harder to debug as it is now ...


From: Peter Stachowski [mailto:peter at tesora.com]
Sent: Monday, May 09, 2016 10:17 AM
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [trove] timeouts in gate-trove-python34-db

Hi Amrith,

We've had a lot of 'new' tests enabled for py34 in the last week - from your results you can see it's running 6x the number of tests (although it's taking 8.5x as long).  It looks like python3 isn't as fast as python2.7?  If so, we may have to do something wrt the 'dangling-mock' detector code so that the tests run faster (I believe we can optimize it now that all the tests have moved over to the new paradigm).


From: Amrith Kumar [mailto:amrith at tesora.com]
Sent: May-08-16 8:42 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [trove] timeouts in gate-trove-python34-db

I'm seeing python34's gate job running very long and sometimes it is timing out at 40m. There is something amiss with this and I've let Victor and Abhishek know about it.

In https://review.openstack.org/#/c/313941/ which is a dummy commit (just changed README.rst) it took 37m.

2016-05-08 21:35:11.438 | Tests running...

2016-05-08 21:35:11.438 |

2016-05-08 21:35:11.438 | Ran 686 tests in 1581.090s

2016-05-08 21:35:11.439 | OK

On the other hand, in other reviews (https://review.openstack.org/#/c/222752/) it takes barely 15m.

2016-05-02 19:26:06.018 | Tests running...

2016-05-02 19:26:06.019 |

2016-05-02 19:26:06.019 | Ran 115 tests in 185.864s

2016-05-02 19:26:06.019 | OK

Running it on my desktop takes a long time as well. I guess we'll have to figure out why this is generating these failures.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160509/c5450e91/attachment.html>

More information about the OpenStack-dev mailing list