Mailing-List: contact notifications-help@yetus.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@yetus.apache.org
Date: Wed, 17 Aug 2016 20:05:20 +0000 (UTC)
From: "Dima Spivak (JIRA)" <jira@apache.org>
To: notifications@yetus.apache.org
Message-ID: <JIRA.12939530.1455635941000.335580.1471464320592@Atlassian.JIRA>
In-Reply-To: <JIRA.12939530.1455635941000@Atlassian.JIRA>
References: <JIRA.12939530.1455635941000@Atlassian.JIRA> <JIRA.12939530.1455635941505@arcas>
Subject: [jira] [Updated] (YETUS-309) pylint plugin false positives
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 17 Aug 2016 20:05:23 -0000


     [ https://issues.apache.org/jira/browse/YETUS-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dima Spivak updated YETUS-309:
------------------------------
    Attachment:     (was: YETUS-309.99.patch)

> 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
>         Attachments: YETUS-309.00.patch, YETUS-309.99.patch
>
>
> 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)