yahoo-eng-team team mailing list archive

[Mark McClain <1197094@xxxxxxxxxxxxxxxxxx>]

@david peraza:  I use tox to run unit tests.  I do end up with eggs from
time to time because I will use nose or the the python test runner.

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

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

Title:
  unit tests consistently fail against master in
  test_network_add_to_dhcp_agent

Status in OpenStack Neutron (virtual network service):
  Invalid

Bug description:
  We are consistently seeing the following failure when trying to run
  unit tests against the master branch:

  quantum.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_add_to_dhcp_agent
  ... FAIL

  ======================================================================
  FAIL: process-returncode
  ----------------------------------------------------------------------
  _StringException: Binary content:
    traceback (test/plain; charset="utf8")

  
  ======================================================================
  FAIL: quantum.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_add_to_dhcp_agent
  ----------------------------------------------------------------------
  _StringException

  ----------------------------------------------------------------------
  Ran 1983 tests in 249.928s

  FAILED (failures=2)

  Running the exact same test using the -d option doesn't encounter a
  failure:

  [openstack@jsbryant-rhel6-db2 quantum]$ ./run_tests.sh -d  quantum.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_add_to_dhcp_agent
  Tests running...

  Ran 1 test in 0.196s
  OK
  [openstack@jsbryant-rhel6-db2 quantum]$ ./run_tests.sh -d  quantum.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_add_to_dhcp_agent
  Tests running...

  Ran 1 test in 0.252s
  OK
  [openstack@jsbryant-rhel6-db2 quantum]$

  I found the following question/discussion on this problem:
  https://answers.launchpad.net/neutron/+question/230219  The suggestion
  of cleaning out the site-packages directory doesn't, however, seem
  help.  I have been running with the -V -f options to reload the
  virtual environment and it doesn't help.  I have also verified that it
  looks like we are the latest testrepository level.  It looks like we
  are:  0.0.15.final.0.

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