[openstack-dev] [Neutron] Neutron py27 test 'FAIL: process-returncode'

Clark Boylan clark.boylan at gmail.com
Wed Feb 12 02:07:30 UTC 2014


On Tue, Feb 11, 2014 at 5:52 PM, Gary Duan <garyduan at gmail.com> wrote:
> Hi,
>
> The patch I submitted for L3 service framework integration fails on jenkins
> test, py26 and py27. The console only gives following error message,
>
> 2014-02-12 00:45:01.710 | FAIL: process-returncode
> 2014-02-12 00:45:01.711 | tags: worker-1
>
> and at the end,
>
> 2014-02-12 00:45:01.916 | ERROR: InvocationError:
> '/home/jenkins/workspace/gate-neutron-python27/.tox/py27/bin/python -m
> neutron.openstack.common.lockutils python setup.py testr --slowest
> --testr-args='
> 2014-02-12 00:45:01.917 | ___________________________________ summary
> ____________________________________
> 2014-02-12 00:45:01.918 | ERROR:   py27: commands failed
>
> I wonder what might be the reason for the failure and how to debug this
> problem?
>
> The patch is at, https://review.openstack.org/#/c/59242/
>
> The console output is,
> http://logs.openstack.org/42/59242/7/check/gate-neutron-python27/e395b06/console.html
>
> Thanks,
>
> Gary
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

I haven't dug into this too far but
http://logs.openstack.org/42/59242/7/check/gate-neutron-python27/e395b06/testr_results.html.gz
seems to offer some clues. Not sure why the console output doesn't
show the additional non exit code errors (possibly a nonstandard
formatter? or a bug?).

Also, cases like this tend to be the test framework completely dying
due to a sys.exit somewhere or similar. This kills the tests and runs
only a small subset of them which seems to be the case here.

Clark



More information about the OpenStack-dev mailing list