Hi Gary- Look into the logs with a search towards your written code keywords..
There might be some issues related to PEP8 or invalid import paths. Hope this helps. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 From: Gary Duan [mailto:garyd...@gmail.com] Sent: Wednesday, February 12, 2014 9:20 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] Neutron py27 test 'FAIL: process-returncode' Clark, You are right. The test must have been bailed out. The question is what I should look for. Even a successful case has a lot of Traceback, ERROR log in subunit_log.txt. Thanks, Gary On Tue, Feb 11, 2014 at 7:19 PM, Clark Boylan <clark.boy...@gmail.com<mailto:clark.boy...@gmail.com>> wrote: On Tue, Feb 11, 2014 at 7:05 PM, Gary Duan <garyd...@gmail.com<mailto:garyd...@gmail.com>> wrote: > Hi, Clark, > > Thanks for your reply. > > I thought the same thing at first, but the page by default only shows the > failed cases. The other 1284 cases were OK. > > Gary > > > On Tue, Feb 11, 2014 at 6:07 PM, Clark Boylan > <clark.boy...@gmail.com<mailto:clark.boy...@gmail.com>> > wrote: >> >> On Tue, Feb 11, 2014 at 5:52 PM, Gary Duan >> <garyd...@gmail.com<mailto:garyd...@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@lists.openstack.org<mailto:OpenStack-dev@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 >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > I picked a different neutron master change and it ran 10k py27 unittests. Pretty sure the test framework is bailing out early here. Clark _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev