N313 hacking check is not being run

Bug #1649297 reported by Maciej Szankin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Confirmed
Low
Unassigned

Bug Description

Description
===========
N313 hacking check has a regex that is not allowing the check to be run.

Steps to reproduce
==================
Change any configuration option to start with lower case letter and run ``tox -e pep8``

Expected result
===============
``tox -e pep8`` command should fail, due to violating N313 hacking check.

Actual result
=============
``tox -e pep8`` passes.

Environment
===========
Current master branch (4728c3e4fde5b5b7b068f60ea410d663deea7db2)

Logs & Configs
==============
None. This check also does not have any UT coverage.

Changed in nova:
assignee: nobody → Maciej Szankin (mszankin)
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/409818

Changed in nova:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on nova (master)

Change abandoned by Maciej Szankin (<email address hidden>) on branch: master
Review: https://review.openstack.org/409818
Reason: Requires more effort than it is worth right now (release time).

Changed in nova:
status: In Progress → Confirmed
assignee: Maciej Szankin (mszankin) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.