By default we capture the logging output stream at INFO level
for unit/functional tests and anything that hits the libvirt
Host.get_capabilities method logs the giant xml host capabilities
string that is defined in the fakelibvirt module. This can cause
subunit parsing to fail because there is too much output in the
buffer.
This change simply stubs out that particular logging call in the
FakeLibvirtFixture class which is used extensively in the more
detailed libvirt tests like LibvirtConnTestCase. If this turns out
to not be good enough we can try stubbing at a more global level
like in the base nova TestCase.
Reviewed: https:/ /review. opendev. org/682133 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=2973faa0706 3d2112ef7459ab0 7cc07e20d74610
Committed: https:/
Submitter: Zuul
Branch: master
commit 2973faa07063d21 12ef7459ab07cc0 7e20d74610
Author: Matt Riedemann <email address hidden>
Date: Fri Sep 13 14:18:25 2019 -0400
libvirt: stub logging of host capabilities
By default we capture the logging output stream at INFO level get_capabilitie s method logs the giant xml host capabilities
for unit/functional tests and anything that hits the libvirt
Host.
string that is defined in the fakelibvirt module. This can cause
subunit parsing to fail because there is too much output in the
buffer.
This change simply stubs out that particular logging call in the Fixture class which is used extensively in the more Case. If this turns out
FakeLibvirt
detailed libvirt tests like LibvirtConnTest
to not be good enough we can try stubbing at a more global level
like in the base nova TestCase.
Change-Id: I38b350bce90800 5161ed7c3eb737f 32076828a37
Related-Bug: #1813147