[
https://issues.apache.org/jira/browse/YETUS-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15425042#comment-15425042
]
Sean Busbey commented on YETUS-309:
-----------------------------------
please feel free. happy to have more contributors. :)
> pylint plugin false positives
> -----------------------------
>
> Key: YETUS-309
> URL: https://issues.apache.org/jira/browse/YETUS-309
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
> Affects Versions: 0.1.0
> Reporter: Sean Busbey
> Assignee: Dima Spivak
>
> the pylint plugin is flagging some changes as failures when the pylint
> utility returns a success return code because of INFO level messages about
> local disables.
> e.g. in a patch that removes all outstanding issues but has to use local
> disables in some cases, test-patch returns a -1 and the diff contains only:
> {code}
> some/path/to/script.py:53: [I0011(locally-disabled), ] Locally disabling
> no-member (E1101)
> some/path/to/script.py:54: [I0011(locally-disabled), ] Locally disabling
> no-member (E1101)
> some/path/to/script.py:55: [I0011(locally-disabled), ] Locally disabling
> no-member (E1101)
> some/path/to/script.py:56: [I0011(locally-disabled), ] Locally disabling
> no-member (E1101)
> some/path/to/script.py:57: [I0011(locally-disabled), ] Locally disabling
> no-member (E1101)
> some/path/to/script.py:58: [I0011(locally-disabled), ] Locally disabling
> no-member (E1101)
> {code}
> In this particular case, the code uses dynamic attributes, which pylint in
> python 2.x can't handle. In general, things at the INFO level (IXXXX)
> shouldn't cause a failure. Or at a minimum personalities should be able to
> opt-in to it not failing without overriding the log output filter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
