Further mock adjustments to deal with intermittent failure
When the py-mysql tox target is run after the py27 tox target it can
sometimes fail because a MagicMock was not properly initialized.
This change more completely fleshes out the mock so that a TypeError
does not occur when a debugging log message is caused. The
specifics of why the logging only happens sometimes are not
understood.
Reviewed: https:/ /review. openstack. org/170092 /git.openstack. org/cgit/ openstack/ ceilometer/ commit/ ?id=931d7a415e8 6f795a5e9fca89a 511a3be641b8d9
Committed: https:/
Submitter: Jenkins
Branch: master
commit 931d7a415e86f79 5a5e9fca89a511a 3be641b8d9
Author: Chris Dent <email address hidden>
Date: Thu Apr 2 12:53:34 2015 +0100
Further mock adjustments to deal with intermittent failure
When the py-mysql tox target is run after the py27 tox target it can
sometimes fail because a MagicMock was not properly initialized.
This change more completely fleshes out the mock so that a TypeError
does not occur when a debugging log message is caused. The
specifics of why the logging only happens sometimes are not
understood.
Change-Id: I99f80d794b757a 0ac05f7a9b53974 ba9913e6e68
Closes-Bug: #1438300