yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1232166@xxxxxxxxxxxxxxxxxx>]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1232166

Title:
  run_tests.sh misleading, broken, and might be unused

Status in OpenStack Neutron (virtual network service):
  Expired

Bug description:
  As per conversation in #openstack-neutron

  124337 #openstack-neutron         mestery | roaet: How are you running the tests?
  124358 #openstack-neutron           roaet | mestery: I am using ./run_tests.sh I used to use tox... maybe I should use tox
  124433 #openstack-neutron         mestery | I don't think run_tests.sh is supported or works anymore.
  124436 #openstack-neutron         mestery | I don't know why it's still there in fact.
  124440 #openstack-neutron         mestery | But someone else will know for sure.
  124443 #openstack-neutron         mestery | I woudl recommend using tox
  124448 #openstack-neutron         mestery | something like this should work: tox -v -epy27
  124507 #openstack-neutron           roaet | Yeah I keep on making the same mistake, using run-tests
  124511 #openstack-neutron           roaet | I'll just use tox.
  124511 #openstack-neutron         mestery | :)
  124513 #openstack-neutron           roaet | my apologies
  124513 #openstack-neutron         mestery | Cool
  124517 #openstack-neutron         mestery | I think you'll have better luck
  124532 #openstack-neutron         mestery | And someone needs to explain to me why run_tests.sh is still there, as you're not the first person to ask this question. :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1232166/+subscriptions