summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorzhoulinhui <df.some@foxmail.com>2020-09-18 00:17:44 +0800
committerzhoulinhui <df.some@foxmail.com>2020-10-16 01:19:48 +0000
commit720230d9ddbcf12b29c5edb91591f3d2cb2c41fb (patch)
tree24740d3c899eaedd7add3cbea9e0935c228c3895
parent3cf0406eae32620788e65b717d1d015f7dc44906 (diff)
downloadoslo-i18n-720230d9ddbcf12b29c5edb91591f3d2cb2c41fb.tar.gz
Fix hacking min version to 3.0.1
flake8 new release 3.8.0 added new checks and gate pep8 job start failing. hacking 3.0.1 fix the pinning of flake8 to avoid bringing in a new version with new checks. Though it is fixed in latest hacking but 2.0 and 3.0 has cap for flake8 as <4.0.0 which mean flake8 new version 3.9.0 can also break the pep8 job if new check are added. To avoid similar gate break in future, we need to bump the hacking min version. - http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html Change-Id: I87fdbf691c0b2b0abdf629b358d875d955b14015
-rw-r--r--test-requirements.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/test-requirements.txt b/test-requirements.txt
index f67ab10..1b99e25 100644
--- a/test-requirements.txt
+++ b/test-requirements.txt
@@ -1,7 +1,7 @@
# 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.
-hacking>=3.0,<3.1.0 # Apache-2.0
+hacking>=3.0.1,<3.1.0 # Apache-2.0
stestr>=2.0.0 # Apache-2.0
oslotest>=3.2.0 # Apache-2.0