[Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3

[Jim Somerville]

On 2020-01-30 12:36 p.m., Bailey, Henry Albert (Al) wrote:
> It should be fine to cherry pick to 3.0
> I am not sure if 2.0 would be a clean pick (we renamed repos at some point)

I attempted the 2.0 cherry pick but it fails with a strange invocation 
error in the zuul check of stx-integ-pylint

https://review.opendev.org/#/c/705077/

Possible chicken and egg issue?

-Jim

> 
> Al
> 
> -----Original Message-----
> From: Jim Somerville [mailto:jim.somerville at windriver.com]
> Sent: Thursday, January 30, 2020 12:19 PM
> To: Bailey, Henry Albert (Al); starlingx
> Subject: Re: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3
> 
> 
> 
> On 2020-01-28 8:53 a.m., Bailey, Henry Albert (Al) wrote:
>> Here you go Jim
>> https://review.opendev.org/#/c/704566/
> 
> Hi Al,
> 
> Is it safe to backport that to r/2.0 and r/3.0?
> 
> -Jim
> 
>>
>> Al
>>
>> -----Original Message-----
>> From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com]
>> Sent: Tuesday, January 28, 2020 8:35 AM
>> To: Somerville, Jim; starlingx
>> Subject: Re: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3
>>
>>
>> A new libvirt-python (6.0.0) was released on Jan 23rd
>> https://pypi.org/project/libvirt-python/#history
>>
>>    and it likely only supports py3
>>
>> I will look into it.    Probably just need an upper constraint.
>>
>> Al
>>
>>
>> -----Original Message-----
>> From: Jim Somerville [mailto:jim.somerville at windriver.com]
>> Sent: Monday, January 27, 2020 5:57 PM
>> To: starlingx
>> Subject: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3
>>
>> Hi Folks,
>>
>> Problem (branch master):
>>
>> - stx-integ-pylint
>> https://zuul.opendev.org/t/openstack/build/c8704619a95443ee8a049985061bfb57
>> : FAILURE in 3m 24s
>>
>> is due to libvirt-python needing python 3 instead of 2, is nothing
>> related to my change.
>>
>> Anyone know how to get this fixed?  CentOS 8 folks, any ideas?
>>
>> Thanks,
>>
>> -Jim
>>
>>
>> -------- Forwarded Message --------
>> Subject: Change in starlingx/integ[master]: Mellanox Driver: Disable use
>> of kernel page pool functionality
>> Date: Mon, 27 Jan 2020 17:39:36 +0000
>> From: Zuul (Code Review) <review at openstack.org>
>> To: Jim Somerville <jim.somerville at windriver.com>
>> CC: Victor Manuel Rodriguez Bahena <vm.rod25 at gmail.com>, Robin Lu
>> <bin1.lu at intel.com>, Brent Rowsell <brent.rowsell at windriver.com>, Steven
>> Webster <steven.webster at windriver.com>, Scott Little
>> <scott.little at windriver.com>, Ghada Khalil <ghada.khalil at windriver.com>,
>> Wendy Mitchell <wendy.mitchell at windriver.com>, Don Penney
>> <don.penney at windriver.com>, Saul Wold <sgw at linux.intel.com>
>>
>> Zuul has posted comments on this change. (
>> https://review.opendev.org/704180 )
>>
>> Change subject: Mellanox Driver: Disable use of kernel page pool
>> functionality
>> ......................................................................
>>
>>
>> Patch Set 1:
>>
>> Build failed (check pipeline).  For information on how to proceed, see
>> http://docs.openstack.org/infra/manual/developers.html#automated-testing
>>
>>
>> - openstack-tox-docs
>> https://zuul.opendev.org/t/openstack/build/cbee2ab21a7c4cf1b123e5da5299fd74
>> : SUCCESS in 4m 04s
>> - openstack-tox-pep8
>> https://zuul.opendev.org/t/openstack/build/11fb173c3490482eb2902a46957e2caa
>> : SUCCESS in 4m 52s
>> - openstack-tox-linters
>> https://zuul.opendev.org/t/openstack/build/1a614a32943143b6bdcbf7a145f05c9e
>> : SUCCESS in 4m 18s
>> - stx-integ-pylint
>> https://zuul.opendev.org/t/openstack/build/c8704619a95443ee8a049985061bfb57
>> : FAILURE in 3m 24s
>>