Keystone is certainly CPU bound while doing crypto operations
(authentication, token creation, token validation, etc), so we're
experimenting with pypy now, but don't have any strong interest in the gate
jobs running *currently*. We might want to add one for keystone at some
point, though.
On
On 11 May 2015 at 23:51, Sean Dague s...@dague.net wrote:
It appears that we've basically run out of interest / time in
realistically keeping pypy working in our system.
With the focus on really getting python 3.4 working, it seems like it
would just be better to drop pypy entirely in the
requirements jobs are stuck as well :(
http://logs.openstack.org/30/170830/6/check/gate-requirements-pypy/732dc33/console.html#_2015-05-11_01_25_22_506
-- dims
On Mon, May 11, 2015 at 6:19 AM, Steven Hardy sha...@redhat.com wrote:
On Mon, May 11, 2015 at 11:52:13AM +0200, Julien Danjou wrote:
On Fri, May 08 2015, Doug Hellmann wrote:
The jobs running unit tests under pypy are failing for several Oslo
libraries for reasons that have nothing to do with the libraries
themselves, as far as I can tell (they pass locally). I have proposed
a change to mark the jobs as non-voting [1]
On Mon, May 11, 2015 at 11:52:13AM +0200, Julien Danjou wrote:
On Fri, May 08 2015, Doug Hellmann wrote:
The jobs running unit tests under pypy are failing for several Oslo
libraries for reasons that have nothing to do with the libraries
themselves, as far as I can tell (they pass
It appears that we've basically run out of interest / time in
realistically keeping pypy working in our system.
With the focus on really getting python 3.4 working, it seems like it
would just be better to drop pypy entirely in the system. In the last
couple of years we've not seen any services
Thanks Sean, filed this review to mark them as non-voting to start with:
https://review.openstack.org/181870
-- dims
On Mon, May 11, 2015 at 7:51 AM, Sean Dague s...@dague.net wrote:
It appears that we've basically run out of interest / time in
realistically keeping pypy working in our system.
The jobs running unit tests under pypy are failing for several Oslo
libraries for reasons that have nothing to do with the libraries
themselves, as far as I can tell (they pass locally). I have proposed
a change to mark the jobs as non-voting [1] until someone can fix
them, but we need a volunteer
