From 6ea20b856c0e39ccf767ffec88f2c0b415ebdc9c Mon Sep 17 00:00:00 2001 From: Dean Troyer Date: Wed, 4 Oct 2017 16:50:03 -0500 Subject: [PATCH] --os-profile option suddenly causes trouble in unit tests I'll be honest, I have no idea yet why importing osprofiler.profiler now fails (shell.py:42). Life is short and its dinnertime... Change-Id: Ic4d1ed6d665e3795fea6d6c6954dd1facab4f5db --- osc_lib/tests/test_shell.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/osc_lib/tests/test_shell.py b/osc_lib/tests/test_shell.py index 13f1822..3c39954 100644 --- a/osc_lib/tests/test_shell.py +++ b/osc_lib/tests/test_shell.py @@ -112,9 +112,10 @@ global_options = { '--os-default-domain': (DEFAULT_DOMAIN_NAME, True, True), '--os-cacert': ('/dev/null', True, True), '--timing': (True, True, False), - '--os-profile': ('SECRET_KEY', True, True), '--os-interface': (DEFAULT_INTERFACE, True, True) } +if shell.osprofiler_profiler: + global_options['--os-profile'] = ('SECRET_KEY', True, True) class TestShellArgV(utils.TestShell):