test: fix wrong usage of config option in test_window
Developers usually use method CONF.set_override to change
config option's value in tests. By default the parameter
enforce_type=False, it doesn't check any type or value of
override. If set enforce_type=True , will check parameter
verride type and value. In production code, oslo_config
always checks config option's value. In short, we test and
run code in different ways. For more details when we set method
set_override with parameter enforce_type=True, please see: http://paste.openstack.org/show/523740/
Reviewed: https:/ /review. openstack. org/334877 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=c23c44a7b78 630fe2cfe531cb6 978e28d05f9344
Committed: https:/
Submitter: Jenkins
Branch: master
commit c23c44a7b78630f e2cfe531cb6978e 28d05f9344
Author: ChangBo Guo(gcb) <email address hidden>
Date: Tue Jun 28 17:10:46 2016 +0800
test: fix wrong usage of config option in test_window
Developers usually use method CONF.set_override to change type=False, it doesn't check any type or value of paste.openstack .org/show/ 523740/
config option's value in tests. By default the parameter
enforce_
override. If set enforce_type=True , will check parameter
verride type and value. In production code, oslo_config
always checks config option's value. In short, we test and
run code in different ways. For more details when we set method
set_override with parameter enforce_type=True, please see:
http://
Related-Bug: 1517839 b9d5daa15e04418 b7111ab9e2f
Change-Id: I0e1929f7e6afa9