Open Stack

On 2017-09-18 22:44, Sean McGinnis wrote:
> On Sun, Sep 17, 2017 at 08:32:00AM +0200, Andreas Jaeger wrote:
>> Currently we use pypy for a couple of projects and many of these fail
>> with the version of pypy that we use.
>>
>> A common error is  "Pypy fails with "RuntimeError: cryptography 1.9 is
>> not compatible with PyPy < 5.3. Please upgrade PyPy to use this library.".
>>
>> Example:
>> http://logs.openstack.org/51/503951/1/check/gate-python-neutronclient-pypy/206ac6a/
>>
>> I propose in https://review.openstack.org/#/c/504748/ to remove pypy
>> from those repos where it fails.
>>
>> Alternative would be investigating what is broken and fix it. Anybody
>> interested to do this?
>>
>> Or should we remove the pypy jobs where they fail. I pushed
>> https://review.openstack.org/504748 up and marked it as WIP, will wait
>> for a week to see outcome of this discussion,
>>
>> Andreas
> 
> I noticed this when we switched over to using cryptography. I think at the time
> the consensus was - meh. IIRC, it's an issue that we use an older version of
> pypy. If system packages are available for a newer version, it probably would
> be good to test that. But I have never seen pypy use in the wild, so I'm not
> sure if it would be worth the effort.

Also, depends on anybody willing to do it.

> Maybe easier just declaring pypy unsupported for service projects?

How do we do this in the best way?

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
       HRB 21284 (AG Nürnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126