Open Stack

Yep, tox is much slower but is beneficial if you're running full test suite
because it runs it on all available cores.
run_tests.sh runs tests sequentially and is moreconvenient when running
separate testsuites/cases

Thanks,
Eugene.


On Thu, Jun 6, 2013 at 7:16 PM, Luke Gorrie <luke at snabb.co> wrote:

> Thanks Eugene and Kyle!
>
> The .venv/bin/python run_tests.py ... trick works for me after . I am in
> business!
>
> 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.
>
>
>
>
>
> On 6 June 2013 16:30, Kyle Mestery (kmestery) <kmestery at cisco.com> wrote:
>
>> Try this Luke:
>>
>> tox -e py27 -v quantum.tests.unit.ml2
>>
>> On Jun 6, 2013, at 9:03 AM, Luke Gorrie <luke at snabb.co> wrote:
>>
>> > Hi Kyle & all,
>> >
>> > I am trying to run the Ml2 unit tests in order to get started with
>> hacking. Can someone tell me the best way please?
>> >
>> > This is what I am trying:
>> >
>> > # ./run_tests.sh -P
>> quantum.tests.unit.ml2.test_ml2_plugin:TestMl2NetworksV2
>> > Running `tools/with_venv.sh python setup.py testr --slowest
>> --testr-args='--subunit
>>  quantum.tests.unit.ml2.test_ml2_plugin:TestMl2NetworksV2'`
>> > invalid command name
>> 'quantum.tests.unit.ml2.test_ml2_plugin:TestMl2NetworksV2'
>> >
>> > 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?
>> >
>> > Any help appreciated :)
>> > -Luke
>> >
>> >
>> >
>> >
>> > On 5 June 2013 15:44, Kyle Mestery (kmestery) <kmestery at cisco.com>
>> wrote:
>> >
>> > On Jun 5, 2013, at 5:11 AM, Luke Gorrie <luke at tail-f.com> wrote:
>> >
>> > > Howdy!
>> > >
>> > > Great work Bob & all on getting the ML2 plugin code onto master,
>> exciting stuff :-)))
>> > >
>> > > 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.
>> > >
>> > > 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.
>> > >
>> > > 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. https://blueprints.launchpad.net/quantum/+spec/tailf-ncs
>> > >
>> > > 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.
>> > >
>> > > 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?
>> > >
>> > > So please give me a ping if you are interested in
>> MechanismDriver+REST, or point me at where I can find people who are :-)
>> > >
>> > > Cheers,
>> > > -Luke
>> > >
>> > 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!
>> >
>> > Looking forward to having you a part of the ML2 team!
>> >
>> > Kyle
>> >
>> > >
>> > > _______________________________________________
>> > > OpenStack-dev mailing list
>> > > OpenStack-dev at lists.openstack.org
>> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>> >
>> > _______________________________________________
>> > OpenStack-dev mailing list
>> > OpenStack-dev at lists.openstack.org
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>> > _______________________________________________
>> > OpenStack-dev mailing list
>> > OpenStack-dev at lists.openstack.org
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130606/285cb9e8/attachment.html>