<div dir="ltr">Yep, tox is much slower but is beneficial if you're running full test suite because it runs it on all available cores. <div>run_tests.sh runs tests sequentially and is moreconvenient when running separate testsuites/cases<div>
<br></div><div style>Thanks,</div><div style>Eugene.</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 6, 2013 at 7:16 PM, Luke Gorrie <span dir="ltr"><<a href="mailto:luke@snabb.co" target="_blank">luke@snabb.co</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks Eugene and Kyle!<div><br></div><div>The .venv/bin/python run_tests.py ... trick works for me after . I am in business!</div>
<div><br></div><div>The tox line seems to spend a long time grinding away without making output -- maybe stuck or maybe just doing a lot of preparation in the background.</div>
<div><br></div><div><br></div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On 6 June 2013 16:30, Kyle Mestery (kmestery) <span dir="ltr"><<a href="mailto:kmestery@cisco.com" target="_blank">kmestery@cisco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Try this Luke:<br>
<br>
tox -e py27 -v quantum.tests.unit.ml2<br>
<div><div><br>
On Jun 6, 2013, at 9:03 AM, Luke Gorrie <<a href="mailto:luke@snabb.co" target="_blank">luke@snabb.co</a>> wrote:<br>
<br>
> Hi Kyle & all,<br>
><br>
> I am trying to run the Ml2 unit tests in order to get started with hacking. Can someone tell me the best way please?<br>
><br>
> This is what I am trying:<br>
><br>
> # ./run_tests.sh -P quantum.tests.unit.ml2.test_ml2_plugin:TestMl2NetworksV2<br>
> Running `tools/with_venv.sh python setup.py testr --slowest --testr-args='--subunit quantum.tests.unit.ml2.test_ml2_plugin:TestMl2NetworksV2'`<br>
> invalid command name 'quantum.tests.unit.ml2.test_ml2_plugin:TestMl2NetworksV2'<br>
><br>
> I don't understand that error. I seem to have the same error if I try to run the BigSwitch plugin tests too, though that was working for me in the Grizzly release, so perhaps run_tests.sh doesn't expect a test name/regex as argument anymore?<br>
><br>
> Any help appreciated :)<br>
> -Luke<br>
><br>
><br>
><br>
><br>
> On 5 June 2013 15:44, Kyle Mestery (kmestery) <<a href="mailto:kmestery@cisco.com" target="_blank">kmestery@cisco.com</a>> wrote:<br>
><br>
> On Jun 5, 2013, at 5:11 AM, Luke Gorrie <<a href="mailto:luke@tail-f.com" target="_blank">luke@tail-f.com</a>> wrote:<br>
><br>
> > Howdy!<br>
> ><br>
> > Great work Bob & all on getting the ML2 plugin code onto master, exciting stuff :-)))<br>
> ><br>
> > I want to use the upcoming ML2 MechanismDriver to make REST requests to an external system. Is anybody else interested in this too and planning related work? If so then perhaps we could join forces.<br>
> ><br>
> > I am flexible with respect to the exact REST API design. In principle I would favor something as close as possible to the raw MechanismDriver API.<br>
> ><br>
> > I am doing this work to integrate with the Tail-f Network Control System (NCS). The blueprint for this work was approved this morning for Havana. <a href="https://blueprints.launchpad.net/quantum/+spec/tailf-ncs" target="_blank">https://blueprints.launchpad.net/quantum/+spec/tailf-ncs</a><br>
> ><br>
> > NCS will be customized to support the REST API that we develop on the OpenStack side. So there are no legacy/compatibility constraints on how the REST API needs to look from my perspective.<br>
> ><br>
> > I am guessing that the maintainers of the BigSwitch plugin would be interested, being as that is also REST-based and may want to be updated to fit into ML2?<br>
> ><br>
> > So please give me a ping if you are interested in MechanismDriver+REST, or point me at where I can find people who are :-)<br>
> ><br>
> > Cheers,<br>
> > -Luke<br>
> ><br>
> Hi Luke, Bob is organizing some sub team meetings around ML2 going forward, we'll be sure to include you in those! Right now, there are 4 blueprints open for continued ML2 work. I'm not aware of anyone doing a controller MechanismDriver yet, so you may have just signed up to be the first!<br>
><br>
> Looking forward to having you a part of the ML2 team!<br>
><br>
> Kyle<br>
><br>
> ><br>
> > _______________________________________________<br>
> > OpenStack-dev mailing list<br>
> > <a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>