We've disabled all the pypy tests across OpenStack because it was
failing, and after 48hrs no one was actually working on any fixes. It's
thus effectively just burning nodes for no value.
It's not clear that there are any active contributors to OpenStack that
find the pypy use case interesting
Excerpts from Sean Dague's message of 2015-05-14 08:53:31 -0400:
We've disabled all the pypy tests across OpenStack because it was
failing, and after 48hrs no one was actually working on any fixes. It's
thus effectively just burning nodes for no value.
The original thread, for reference:
On 15 May 2015 at 00:53, Sean Dague s...@dague.net wrote:
We've disabled all the pypy tests across OpenStack because it was
failing, and after 48hrs no one was actually working on any fixes. It's
thus effectively just burning nodes for no value.
It's not clear that there are any active
On Thu, May 14, 2015, at 05:53 AM, Sean Dague wrote:
We've disabled all the pypy tests across OpenStack because it was
failing, and after 48hrs no one was actually working on any fixes. It's
thus effectively just burning nodes for no value.
I think my change to upgrade virtualenv on our test
