yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1181925] Re: cannot print debug messages in tests (trivial)

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>
Date: Wed, 29 May 2013 11:09:30 -0000
Reply-to: Bug 1181925 <1181925@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: quantum
       Status: Fix Committed => Fix Released

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

Title:
  cannot print debug messages in tests (trivial)

Status in OpenStack Quantum (virtual network service):
  Fix Released

Bug description:
  We cannot get debug messages in the most unit tests that use BaseTestCase in quantum/tests/base.py .
  In BaseTestCase, fixtures.FakeLogger was used with its default logging level (INFO) instead of quantum/openstack logger.
  So, even though setting debug=True in quantum/tests/etc/quantum.conf.test , we cannot get DEBUG messages.

  I think it is useful that there is a option to show DEBUG messages in those unit tests, especially when you run individual tests for debugging.
  # The default should be kept in INFO, because I got over 80MB output by "tox -e py27" with setting FakeLogger level to DEBUG.

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