[ 
https://issues.apache.org/jira/browse/YETUS-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15425321#comment-15425321
 ] 

Yetus QA commented on YETUS-309:
--------------------------------

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 15m 
16s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} pylint {color} | {color:green}  0m  
3s{color} | {color:green} There were no new pylint issues. {color} |
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green}  0m 
 0s{color} | {color:green} There were no new shellcheck issues. {color} |
| {color:green}+1{color} | {color:green} shelldocs {color} | {color:green}  0m  
0s{color} | {color:green} There were no new shelldocs issues. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
 0s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 15m 24s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.11.2 Server=1.11.2 Image:yetus/yetus:e4e4903 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12824223/YETUS-309.99.patch |
| JIRA Issue | YETUS-309 |
| Optional Tests |  pylint  shellcheck  shelldocs  |
| uname | Linux a71bd4ded47a 3.13.0-92-generic #139-Ubuntu SMP Tue Jun 28 
20:42:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | nobuild |
| git revision | master / 6f3aa7a |
| shellcheck | v0.4.4 |
| pylint | v1.6.4 |
| modules | C: . U: . |
| Console output | 
https://builds.apache.org/job/PreCommit-YETUS-Build/472/console |
| Powered by | Apache Yetus 0.4.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> 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)

Reply via email to