Re: [openstack-dev] [Neutron][IPv6] tox error
Hi, Randy: Try this command to install pyudev library…. sudo pip install pyudev Let me know whether it works or not. Good luck! Shixiong Shixiong Shang !--- Stay Hungry, Stay Foolish ---! On Feb 27, 2014, at 9:09 PM, Randy Tuttle wrote: > Clark/Sean/Shixiong... > > I have the same error, and tried to import > neutron.tests.unit.linuxbridge.test_lb_neutron_agent (no error4 prefix). I > get the following > > (py27)rantuttl-mac:bin rtuttle$ python > Python 2.7.5 (v2.7.5:ab05e7dd2788, May 13 2013, 13:18:45) > [GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin > Type "help", "copyright", "credits" or "license" for more information. > >>> import neutron.tests.unit.linuxbridge.test_lb_neutron_agent > Traceback (most recent call last): > File "", line 1, in > File > "/Users/rtuttle/projects/neutron/neutron/tests/unit/linuxbridge/test_lb_neutron_agent.py", > line 29, in > from neutron.plugins.linuxbridge.agent import linuxbridge_neutron_agent > File > "/Users/rtuttle/projects/neutron/neutron/plugins/linuxbridge/agent/linuxbridge_neutron_agent.py", > line 33, in > import pyudev > ImportError: No module named pyudev > >>> > > Looks like it wants pyudev, which is not anywhere that I can find, and is not > in requirements.txt. > > Code slice. > import distutils.version as dist_version > import os > import platform > import sys > import time > > import eventlet > from oslo.config import cfg > import pyudev > > from neutron.agent import l2population_rpc as l2pop_rpc > from neutron.agent.linux import ip_lib > > > Still digging into it... > > Randy > > > > On Thu, Feb 27, 2014 at 3:10 PM, Clark Boylan wrote: > On Thu, Feb 27, 2014 at 11:39 AM, Collins, Sean > wrote: > > Shixiong Shang and I ran into this problem with Tox today while we were > > pair programming, and I've also seen similar barfs on my DevStack lab > > boxes - it's quite a mess. Frankly I've moved to using nosetests as a > > workaround, and have added it to the developer docs. > > > > We really do need to figure out how to make Tox and Testr give more > > useful failure output - it's so huge it makes my iTerm2 window lock up > > when I try and do an incremental search on the output. > > > > Help from a Testr / Tox guru would be appreciated. > > > > -- > > Sean M. Collins > > ___ > > OpenStack-dev mailing list > > OpenStack-dev@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > These failures are a result of testr or discover (depending on the > step in the test process, discovery happens first) running into python > import failures. In the example above it looks like > neutron.tests.unit. > linuxbridge.test_lb_neutron_agent failed to import. You can spin up a > python interpreter and try importing that to debug (note that is what > you tried to do but I believe errors4 is part of the error message and > not the thing that couldn't be imported). Flake8 may also catch the > problem. Lifeless has laid the groundwork to fix this upstream in > testtools [0], but I don't think the corresponding testrepository > improvements have been released yet. You can however install > testrepository from source [1] and see if that solves your problem. > > Without seeing the code in question it is really hard to debug any > further. If nosetests does work that would indicate a possible > intertest dependency that nose resolves by running tests in a > particular order which is different than the order used by testr. > Finally, when using the python executable from a virtualenv you don't > want to be in the virtualenv's bin dir. To do a proper import test you > want to be in the root dir of the repository `cd ~/github/neutron` the > either activate the virtualenv and run python or skip activation and > do `.tox/py27/bin/python` to run the virtualenv's python binary. > > [0] > https://github.com/testing-cabal/testtools/commit/6da4893939c6fd2d732bb20a4ac50db2fe639132 > [1] https://launchpad.net/testrepository/ > > Hope this helps, > Clark > > ___ > OpenStack-dev mailing list > 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 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][IPv6] tox error
Clark/Sean/Shixiong... I have the same error, and tried to import neutron.tests.unit.linuxbridge.test_lb_neutron_agent (no error4 prefix). I get the following (py27)rantuttl-mac:bin rtuttle$ python Python 2.7.5 (v2.7.5:ab05e7dd2788, May 13 2013, 13:18:45) [GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import neutron.tests.unit.linuxbridge.test_lb_neutron_agent Traceback (most recent call last): File "", line 1, in File "/Users/rtuttle/projects/neutron/neutron/tests/unit/linuxbridge/test_lb_neutron_agent.py", line 29, in from neutron.plugins.linuxbridge.agent import linuxbridge_neutron_agent File "/Users/rtuttle/projects/neutron/neutron/plugins/linuxbridge/agent/linuxbridge_neutron_agent.py", line 33, in import pyudev ImportError: No module named pyudev >>> Looks like it wants pyudev, which is not anywhere that I can find, and is not in requirements.txt. Code slice. import distutils.version as dist_version import os import platform import sys import time import eventlet from oslo.config import cfg import pyudev from neutron.agent import l2population_rpc as l2pop_rpc from neutron.agent.linux import ip_lib Still digging into it... Randy On Thu, Feb 27, 2014 at 3:10 PM, Clark Boylan wrote: > On Thu, Feb 27, 2014 at 11:39 AM, Collins, Sean > wrote: > > Shixiong Shang and I ran into this problem with Tox today while we were > > pair programming, and I've also seen similar barfs on my DevStack lab > > boxes - it's quite a mess. Frankly I've moved to using nosetests as a > > workaround, and have added it to the developer docs. > > > > We really do need to figure out how to make Tox and Testr give more > > useful failure output - it's so huge it makes my iTerm2 window lock up > > when I try and do an incremental search on the output. > > > > Help from a Testr / Tox guru would be appreciated. > > > > -- > > Sean M. Collins > > ___ > > OpenStack-dev mailing list > > OpenStack-dev@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > These failures are a result of testr or discover (depending on the > step in the test process, discovery happens first) running into python > import failures. In the example above it looks like > neutron.tests.unit. > linuxbridge.test_lb_neutron_agent failed to import. You can spin up a > python interpreter and try importing that to debug (note that is what > you tried to do but I believe errors4 is part of the error message and > not the thing that couldn't be imported). Flake8 may also catch the > problem. Lifeless has laid the groundwork to fix this upstream in > testtools [0], but I don't think the corresponding testrepository > improvements have been released yet. You can however install > testrepository from source [1] and see if that solves your problem. > > Without seeing the code in question it is really hard to debug any > further. If nosetests does work that would indicate a possible > intertest dependency that nose resolves by running tests in a > particular order which is different than the order used by testr. > Finally, when using the python executable from a virtualenv you don't > want to be in the virtualenv's bin dir. To do a proper import test you > want to be in the root dir of the repository `cd ~/github/neutron` the > either activate the virtualenv and run python or skip activation and > do `.tox/py27/bin/python` to run the virtualenv's python binary. > > [0] > https://github.com/testing-cabal/testtools/commit/6da4893939c6fd2d732bb20a4ac50db2fe639132 > [1] https://launchpad.net/testrepository/ > > Hope this helps, > Clark > > ___ > OpenStack-dev mailing list > 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
Re: [openstack-dev] [Neutron][IPv6] tox error
On Thu, Feb 27, 2014 at 11:39 AM, Collins, Sean wrote: > Shixiong Shang and I ran into this problem with Tox today while we were > pair programming, and I've also seen similar barfs on my DevStack lab > boxes - it's quite a mess. Frankly I've moved to using nosetests as a > workaround, and have added it to the developer docs. > > We really do need to figure out how to make Tox and Testr give more > useful failure output - it's so huge it makes my iTerm2 window lock up > when I try and do an incremental search on the output. > > Help from a Testr / Tox guru would be appreciated. > > -- > Sean M. Collins > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev These failures are a result of testr or discover (depending on the step in the test process, discovery happens first) running into python import failures. In the example above it looks like neutron.tests.unit. linuxbridge.test_lb_neutron_agent failed to import. You can spin up a python interpreter and try importing that to debug (note that is what you tried to do but I believe errors4 is part of the error message and not the thing that couldn't be imported). Flake8 may also catch the problem. Lifeless has laid the groundwork to fix this upstream in testtools [0], but I don't think the corresponding testrepository improvements have been released yet. You can however install testrepository from source [1] and see if that solves your problem. Without seeing the code in question it is really hard to debug any further. If nosetests does work that would indicate a possible intertest dependency that nose resolves by running tests in a particular order which is different than the order used by testr. Finally, when using the python executable from a virtualenv you don't want to be in the virtualenv's bin dir. To do a proper import test you want to be in the root dir of the repository `cd ~/github/neutron` the either activate the virtualenv and run python or skip activation and do `.tox/py27/bin/python` to run the virtualenv's python binary. [0] https://github.com/testing-cabal/testtools/commit/6da4893939c6fd2d732bb20a4ac50db2fe639132 [1] https://launchpad.net/testrepository/ Hope this helps, Clark ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][IPv6] tox error
Shixiong Shang and I ran into this problem with Tox today while we were pair programming, and I've also seen similar barfs on my DevStack lab boxes - it's quite a mess. Frankly I've moved to using nosetests as a workaround, and have added it to the developer docs. We really do need to figure out how to make Tox and Testr give more useful failure output - it's so huge it makes my iTerm2 window lock up when I try and do an incremental search on the output. Help from a Testr / Tox guru would be appreciated. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][IPv6] tox error
When I see a fox, it is usually running b-( = )) Sent from my iPhone > On Feb 24, 2014, at 6:08 PM, Shixiong Shang > wrote: > > Hi, guys: > > I run into this error while running fox…..but it gave me this error…Seems > like it is related to Neutron LB. Did you see this issue before? If so, how > to fix it? > > Thanks! > > Shixiong > > > shshang@net-ubuntu2:~/github/neutron$ tox -v -e py27 > ……... > tests.unit.test_wsgi.XMLDictSerializerTest.test_xml_with_utf8\xa2\xbe\xf7u\xb3 > `@d\x17text/plain;charset=utf8\rimport > errors4neutron.tests.unit.linuxbridge.test_lb_neutron_agent\x85\xc5\x1a\\', > stderr=None > error: testr failed (3) > ERROR: InvocationError: '/home/shshang/github/neutron/.tox/py27/bin/python -m > neutron.openstack.common.lockutils python setup.py testr --slowest > --testr-args=' > > summary > > ERROR: py27: commands failed > > > (py27)shshang@net-ubuntu2:~/github/neutron/.tox/py27/bin$ python > Python 2.7.5+ (default, Sep 19 2013, 13:48:49) > [GCC 4.8.1] on linux2 > Type "help", "copyright", "credits" or "license" for more information. import errors4neutron.tests.unit.linuxbridge.test_lb_neutron_agent > Traceback (most recent call last): > File "", line 1, in > ImportError: No module named > errors4neutron.tests.unit.linuxbridge.test_lb_neutron_agent > > > > > > ___ > OpenStack-dev mailing list > 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
[openstack-dev] [Neutron][IPv6] tox error
Hi, guys: I run into this error while running fox…..but it gave me this error…Seems like it is related to Neutron LB. Did you see this issue before? If so, how to fix it? Thanks! Shixiong shshang@net-ubuntu2:~/github/neutron$ tox -v -e py27 ……... tests.unit.test_wsgi.XMLDictSerializerTest.test_xml_with_utf8\xa2\xbe\xf7u\xb3 `@d\x17text/plain;charset=utf8\rimport errors4neutron.tests.unit.linuxbridge.test_lb_neutron_agent\x85\xc5\x1a\\', stderr=None error: testr failed (3) ERROR: InvocationError: '/home/shshang/github/neutron/.tox/py27/bin/python -m neutron.openstack.common.lockutils python setup.py testr --slowest --testr-args=' summary ERROR: py27: commands failed (py27)shshang@net-ubuntu2:~/github/neutron/.tox/py27/bin$ python Python 2.7.5+ (default, Sep 19 2013, 13:48:49) [GCC 4.8.1] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import errors4neutron.tests.unit.linuxbridge.test_lb_neutron_agent Traceback (most recent call last): File "", line 1, in ImportError: No module named errors4neutron.tests.unit.linuxbridge.test_lb_neutron_agent ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
