New flake8 3.6.0 version triggering tox failures
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Bart Wensley |
Bug Description
Brief Description
-----------------
Late on Oct 23rd a new flake8 version (3.6.0) was released. The best way to handle this is to keep the StarlingX repos at the current flake8 version which is <3.6.0 and create a StoryBoard to track addressing any flake8 issues due to the new v3.6.0 release.
Severity
--------
Critical - StarlingX commits will be blocked until this is addressed.
Steps to Reproduce
------------------
Execute tox on a StarlingX repo
Expected Behavior
------------------
tox should pass
Actual Behavior
----------------
tox is failing as the new version identifies new standard/issues; this blocks all new commits to StarlingX repos
Reproducibility
---------------
100% reproducible
System Configuration
-------
All
Branch/Pull Time/Commit
-------
master or r2018.10 Oct 24th
Timestamp/Logs
--------------
n/a
Changed in starlingx: | |
assignee: | nobody → Bart Wensley (bartwensley) |
tags: | added: stx.zuul |
Changed in starlingx: | |
importance: | Undecided → High |
Changed in starlingx: | |
status: | In Progress → Fix Released |
tags: |
added: stx.2019.05 removed: stx.2019.03 |
tags: |
added: stx.2.0 removed: stx.2019.05 |
Fix proposed to branch: master /review. openstack. org/613063
Review: https:/