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

Hadoop QA commented on HBASE-19098:
-----------------------------------

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
11s{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  
4s{color} | {color:green} There were no new pylint 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 
10s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}  0m 34s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-19098 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12894202/HBASE-19098.0.patch |
| Optional Tests |  asflicense  pylint  |
| uname | Linux 45801b0525e2 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 
13:48:03 UTC 2016 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
 |
| git revision | master / 459202bab0 |
| pylint | v1.6.5 |
| modules | C: . U: . |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/9428/console |
| Powered by | Apache Yetus 0.4.0   http://yetus.apache.org |


This message was automatically generated.



> Python based compatiblity checker fails if git repo does not have a remote 
> named 'origin'
> -----------------------------------------------------------------------------------------
>
>                 Key: HBASE-19098
>                 URL: https://issues.apache.org/jira/browse/HBASE-19098
>             Project: HBase
>          Issue Type: Bug
>          Components: tooling
>            Reporter: Andrew Purtell
>            Assignee: Sean Busbey
>            Priority: Critical
>         Attachments: HBASE-19098.0.patch
>
>
> The new Python based compatibility checker will fail if the local git repo 
> does not have a remote named "origin". I develop with multiple upstream repos 
> and rename them according to a custom convention. If the requirement that an 
> upstream named "origin" must be present could be removed, that would be good, 
> or otherwise this should be documented next to the example usage in the 
> python source. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to