[Starlingx-discuss] [Zuul] failure on review in stx-config project

Andy Ning andy.ning at windriver.com
Thu Mar 14 20:57:09 UTC 2019


Thanks Jeremy, see my comments inline ...

Andy

On 2019-03-14 04:02 PM, Jeremy Stanley wrote:
> On 2019-03-14 15:39:23 -0400 (-0400), Andy Ning wrote:
>> I have a review https://review.openstack.org/#/c/642488/2 with small changes
>> to sysinv. sysinv-tox-py27 and sysinv-tox-py35 failed for this review.
>> However the failure doesn't seem to be related to my changes. The test
>> output has traceback like:
> [...]
>> 2019-03-14 15:56:10.819308 | ubuntu-bionic |         from psycopg2._psycopg
>> import (                     # noqa
>> 2019-03-14 15:56:10.819740 | ubuntu-bionic |     ImportError: /tmp/zuul_sysinvtox/py27/local/lib/python2.7/site-packages/psycopg2/.libs/libresolv-2-c4c53def.5.so:
>> symbol __res_maybe_init version GLIBC_PRIVATE not defined in file libc.so.6
>> with link time reference
>> 2019-03-14 15:56:10.819785 | ubuntu-bionic |
>>
>> Also, local run of tox py27 and py35 both passed.
>>
>> Anybody knows what's going wrong? Any fix is in progress?
> As of roughly 22:00 UTC (on Wednesday, March 13), the default
> nodeset in the opendev/base-jobs repository was updated from
> ubuntu-xenial (16.04 LTS) to ubuntu-bionic (18.04 LTS).
>
> In the case of the sysinv-tox-py35 job you almost certainly need to
> set an explicit "nodeset: ubuntu-xenial" so that it runs on a
> platform with actually provides a Python 3.5 interpreter
> (ubuntu-bionic only provides 3.6 and 3.7).
>
> For the sysinv-tox-py27 psycopg2 error above, it looks like it's
> attempting to use a libresolv build which references symbols from a
> different libc. Are you maybe installing bundled libraries
> previously built on an ubuntu-xenial node?
>

[AN]: As developer I don't install anything, I submit my source code 
changes to gerrit as review, and Zuul is triggered to run to verify if 
my change break tox. Where tox runs the tests and what its environment 
like is transparent to (as least for me until now :)). So I'm not sure 
how I could do what you suggest.

>
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190314/57cc8b06/attachment.html>


More information about the Starlingx-discuss mailing list