At the moment the detector is still doing a useful job and I don't think
we can get rid of it just yet.
Peter
-Original Message-
From: Victor Stinner [mailto:vstin...@redhat.com]
Sent: May-16-16 12:10 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re:
> -Original Message-
> From: Victor Stinner [mailto:vstin...@redhat.com]
> Sent: Monday, May 16, 2016 12:10 PM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev] [trove] timeouts in gate-trove-python34-db
>
> Le
ck.org
Subject: Re: [openstack-dev] [trove] timeouts in gate-trove-python34-db
Le 16/05/2016 16:12, Peter Stachowski a écrit :
> Amrith is right though - python34 is *much* slower running this check
> (and somewhat in general) than python27. Maybe that doesn't translate
> into real-
Le 16/05/2016 16:12, Peter Stachowski a écrit :
We're aware that there are ways to mock (and un-mock) correctly.
We're trying to make sure that all our new test code follows those
patterns. We also decided that it wouldn't make sense to change all
the working tests to use the 'right' methods as
Le 16/05/2016 16:12, Peter Stachowski a écrit :
Amrith is right though - python34 is *much* slower running this check
(and somewhat in general) than python27. Maybe that doesn't
translate into real-world performance data, but it has made me a bit
nervous nonetheless.
IMHO we should look more c
Le 09/05/2016 16:16, Peter Stachowski a écrit :
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 h
ade me a bit nervous nonetheless.
Peter
-Original Message-
From: Victor Stinner [mailto:vstin...@redhat.com]
Sent: May-16-16 9:38 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [trove] timeouts in gate-trove-python34-db
Le 16/05/2016 1
Le 16/05/2016 13:52, Amrith Kumar a écrit :
IMHO the strange mock detector code must be removed. It is very
slow and I don't understand its purpose.
[amrith] It serves and has served a very useful purpose and that is
to detect bad tests where code has (and we've had lots of trouble
with this) e
> -Original Message-
> From: Victor Stinner [mailto:vstin...@redhat.com]
> Sent: Monday, May 16, 2016 7:20 AM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev] [trove] timeouts in gate-trove-python34-db
>
> Hi,
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
Stachowski [mailto:pe...@tesora.com]
Sent: Monday, May 09, 2016 10:17 AM
To: OpenStack Development Mailing List (not for usage questions)
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
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.
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 2
13 matches
Mail list logo
