zaza normally runs libjuju async functions in a background thread to enable zaza to be blocking, but keep the libjuju async functions 'ticking over' between blocking calls. This can break unit tests as starting the zaza background thread will hang unless it is cleaned up. A simple solution is just to use zaza in non-threaded mode in the unit tests, and zaza provides a mechanism for this via zaza.RUN_LIBJUJU_IN_THREAD = False.
19 lines
669 B
Python
19 lines
669 B
Python
# Copyright 2018 Canonical Ltd.
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
# you may not use this file except in compliance with the License.
|
|
# You may obtain a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
# See the License for the specific language governing permissions and
|
|
# limitations under the License.
|
|
|
|
# force zaza to not use threads for async
|
|
import zaza
|
|
|
|
zaza.RUN_LIBJUJU_IN_THREAD = False
|