70f144abde
We have a couple of issues blocking tooz test jobs right now. This is a combination of two commits that fix the problem. Cap grpcio<1.16.0 1.16.0 introduces a bug that is causing our etcd3 tests to fail on a consistent basis. Until that is resolved we can't use any higher versions of grpcio. 1.0.0 is used as the lower bound on the assumption that any version of the current major release will work. Since we weren't setting a bound before that seems relatively safe. Partial-Bug: 1808046 Fix requirements The requirements check job is failing on a couple of the entries in this project. enum34 needs a lower bound, and futurist has an exclusion that isn't in global-requirements. enum34 is given the same lower bound as oslo.upgradecheck, and futurist's lower bound is increased to the last global lower bound (before lower bounds were removed), which eliminates the need for the exclusion. Change-Id: I1b279e138325b596f5ec2c61717029d2f7bdd075 Depends-On: https://review.openstack.org/#/c/624759/
17 lines
679 B
Plaintext
17 lines
679 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>=1.6 # Apache-2.0
|
|
stevedore>=1.16.0 # Apache-2.0
|
|
six>=1.9.0 # MIT
|
|
enum34>=1.0.4;python_version=='2.7' or python_version=='2.6' or python_version=='3.3' # BSD
|
|
voluptuous>=0.8.9 # BSD License
|
|
msgpack>=0.4.0 # Apache-2.0
|
|
fasteners>=0.7 # Apache-2.0
|
|
tenacity>=3.2.1 # Apache-2.0
|
|
futures>=3.0;python_version=='2.7' or python_version=='2.6' # BSD
|
|
futurist>=1.2.0 # Apache-2.0
|
|
oslo.utils>=3.15.0 # Apache-2.0
|
|
oslo.serialization>=1.10.0 # Apache-2.0
|
|
grpcio>=1.0.0,<1.16.0
|