3f1314674d
This switching our retry mechanism over from the retrying library to the tenacity library. Retrying has been active for a few years now and appears to be no longer maintained. This has a small behavior change in that before we were applying an exponential backoff to the first time a retry was needed. This no longer happens, but retries will exponentially back off with each retry. Also cleaned up some minor nits with unit test assert argument order. Closes-bug: #1635397 Change-Id: I24cab206b16e63859d4886c55d40a03d398ce30d Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
17 lines
623 B
Plaintext
17 lines
623 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
|
|
pbr!=2.1.0,>=2.0.0 # Apache-2.0
|
|
eventlet!=0.18.3,!=0.20.1,!=0.21.0,!=0.23.0,!=0.25.0,>=0.18.2 # MIT
|
|
oslo.concurrency>=3.26.0 # Apache-2.0
|
|
oslo.log>=3.36.0 # Apache-2.0
|
|
oslo.i18n>=3.15.3 # Apache-2.0
|
|
oslo.privsep>=1.32.0 # Apache-2.0
|
|
oslo.service!=1.28.1,>=1.24.0 # Apache-2.0
|
|
oslo.utils>=3.33.0 # Apache-2.0
|
|
requests>=2.14.2 # Apache-2.0
|
|
six>=1.10.0 # MIT
|
|
tenacity>=6.0.0 # Apache-2.0
|
|
os-win>=3.0.0 # Apache-2.0
|