On 13/05/2019 20:31, Andrew Grimberg wrote:
> On 5/11/19 1:40 AM, Robert Varga wrote:
>> Hello,
>>
>> https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-tox-verify-sodium/132/console.log.gz
>> failed for reasons I can only blame on infra:
> 
> It's not an infra issue. The upstream of Pygments released a version
> recently that explicitly disallows the version of Python that is
> installed on the systems. Pinning pygments in the tox.ini takes care of
> this problem.

I beg to disagree. While the patch the immediate issue for netvirt, it
does nothing to address the root cause. See below.

> 
>>> coala installdeps: coala==0.11.0, coala-bears==0.11.0
>>> ERROR: invocation failed (exit code 1), logfile: 
>>> /w/workspace/netvirt-tox-verify-sodium/.tox/coala/log/coala-1.log
>>
>> which seems to be caused by:
>>
>>> Collecting Pygments~=2.1 (from coala==0.11.0)
>>>   Downloading 
>>> https://nexus3.opendaylight.org/repository/PyPi/packages/6e/00/c5cb5fc7c047da4af049005d0146b3a961b1a25d9cefbbe24bf0882a11ad/Pygments-2.4.0-py2.py3-none-any.whl
>>>  (882kB)
>>> Pygments requires Python '>=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*, 
>>> !=3.4.*' but the running Python is 3.4.9
>>
>> Can someone take a look, please?
> 
> I was just looking over the tox.ini file Faseela got a change merged
> over the weekend that resolves the pinning issue.

Right, and all projects using tox need to do the same -- which makes it
a cross-cutting concern worth investigating.

Python-3.4.9 has reached End Of Life on August 2, 2018, which makes this
very much an infra issue.

I am not sure where we are getting Python-3.4.9 from, but there is
python3.6 available for CentOS here:

http://mirror.centos.org/centos/7/sclo/x86_64/rh/rh-python36/

if that is not usable, there is a Python-3.5 available here:

http://mirror.centos.org/centos/7/sclo/x86_64/sclo/sclo-python35/

At any rate, this needs to be on infra's dashboard and it certainly is
not something infra has no hand in -- pinning to old versions is *not*
the way forward.

What python versions are we installing and why are we not using SCLo?

Regards,
Robert

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
infrastructure mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/infrastructure

Reply via email to