New version of flake8 breaks zuul for sysinv
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Critical
|
Al Bailey |
Bug Description
Brief Description
-----------------
On May 11, 2020 a new flake8 and pycodestyle were released on pypi.
Those components are typically pulled in by 'hacking' in the test-requirements.
Reviews that normally pass, are now failing as different checks are now performed.
Severity
--------
Major. Blocks any code submissions from being able to merge in stx/config
Steps to Reproduce
------------------
cd stx/config/
tox -e flake8 --recreate
Expected Behavior
------------------
Tox and Zuul should pass.
Actual Behavior
----------------
Zuul pep8 reports new errors that it did not previously report.
Reproducibility
---------------
Dev Env. Happens with a 'fresh' tox env such as what zuul uses.
System Configuration
-------
N/A
Branch/Pull Time/Commit
-------
After May 11
Last Pass
---------
Yes. Any zuul reviews prior to May 11.
Timestamp/Logs
--------------
./sysinv/
./sysinv/
./sysinv/
./sysinv/
./sysinv/
./sysinv/
Test Activity
-------------
cd sysinv
tox -e flake8 --recreate
Workaround
----------
There isn't one. Either a code change is required, which introduces risk to currently working code. Or setting the upper version is required which allows the code to act as it already was.
Other openstack projects (including 'hacking') are setting the upper limit
https:/
Changed in starlingx: | |
assignee: | nobody → Al Bailey (albailey1974) |
Fix proposed to branch: master /review. opendev. org/727396
Review: https:/