[jira] [Commented] (HBASE-12151) Make dev scripts executable

2014-10-02 Thread Hudson (JIRA)

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

Hudson commented on HBASE-12151:


FAILURE: Integrated in HBase-TRUNK #5613 (See 
[https://builds.apache.org/job/HBase-TRUNK/5613/])
HBASE-12151 Set mode to 755 on executable scripts in dev-support directory 
(mstanleyjones: rev 7219471081ab5f65ad7ae3b2deeb3c1659922102)
* dev-support/jdiffHBasePublicAPI_common.sh
* dev-support/publish_hbase_website.sh
* dev-support/jenkinsEnv.sh
* dev-support/hbase_docker.sh


> Make dev scripts executable
> ---
>
> Key: HBASE-12151
> URL: https://issues.apache.org/jira/browse/HBASE-12151
> Project: HBase
>  Issue Type: Bug
>  Components: scripts
>Reporter: Misty Stanley-Jones
>Assignee: Misty Stanley-Jones
>Priority: Minor
> Fix For: 2.0.0, 0.99.1
>
> Attachments: HBASE-12151.patch
>
>
> Is there any reason not to make dev-support/*.sh executable? It would make it 
> possible to sym-link to them from a directory in the executable path for 
> easier execution of the definitive scripts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12151) Make dev scripts executable

2014-10-02 Thread Hudson (JIRA)

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

Hudson commented on HBASE-12151:


FAILURE: Integrated in HBase-1.0 #266 (See 
[https://builds.apache.org/job/HBase-1.0/266/])
HBASE-12151 Set mode to 755 on executable scripts in dev-support directory 
(mstanleyjones: rev a43f111f0d9a98f6814cbf5ded08239ef8362da5)
* dev-support/publish_hbase_website.sh
* dev-support/jdiffHBasePublicAPI_common.sh
* dev-support/jenkinsEnv.sh
* dev-support/hbase_docker.sh


> Make dev scripts executable
> ---
>
> Key: HBASE-12151
> URL: https://issues.apache.org/jira/browse/HBASE-12151
> Project: HBase
>  Issue Type: Bug
>  Components: scripts
>Reporter: Misty Stanley-Jones
>Assignee: Misty Stanley-Jones
>Priority: Minor
> Fix For: 2.0.0, 0.99.1
>
> Attachments: HBASE-12151.patch
>
>
> Is there any reason not to make dev-support/*.sh executable? It would make it 
> possible to sym-link to them from a directory in the executable path for 
> easier execution of the definitive scripts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12151) Make dev scripts executable

2014-10-02 Thread stack (JIRA)

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

stack commented on HBASE-12151:
---

+1

> Make dev scripts executable
> ---
>
> Key: HBASE-12151
> URL: https://issues.apache.org/jira/browse/HBASE-12151
> Project: HBase
>  Issue Type: Bug
>  Components: scripts
>Reporter: Misty Stanley-Jones
>Assignee: Misty Stanley-Jones
>Priority: Minor
> Attachments: HBASE-12151.patch
>
>
> Is there any reason not to make dev-support/*.sh executable? It would make it 
> possible to sym-link to them from a directory in the executable path for 
> easier execution of the definitive scripts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12151) Make dev scripts executable

2014-10-01 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-12151:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672466/HBASE-12151.patch
  against trunk revision .
  ATTACHMENT ID: 12672466

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 lineLengths{color}.  The patch does not introduce lines 
longer than 100

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

 {color:red}-1 core tests{color}.  The patch failed these unit tests:
   
org.apache.hadoop.hbase.master.TestDistributedLogSplitting

 {color:red}-1 core zombie tests{color}.  There are 2 zombie test(s):   
at 
org.apache.hadoop.hbase.mapreduce.TestLoadIncrementalHFiles.testSimpleLoad(TestLoadIncrementalHFiles.java:100)
at 
org.apache.hadoop.hbase.mapreduce.TestLoadIncrementalHFilesSplitRecovery.testSplitWhileBulkLoadPhase(TestLoadIncrementalHFilesSplitRecovery.java:339)

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11180//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11180//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11180//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11180//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11180//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11180//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11180//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11180//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11180//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11180//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11180//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11180//console

This message is automatically generated.

> Make dev scripts executable
> ---
>
> Key: HBASE-12151
> URL: https://issues.apache.org/jira/browse/HBASE-12151
> Project: HBase
>  Issue Type: Bug
>  Components: scripts
>Reporter: Misty Stanley-Jones
>Assignee: Misty Stanley-Jones
>Priority: Minor
> Attachments: HBASE-12151.patch
>
>
> Is there any reason not to make dev-support/*.sh executable? It would make it 
> possible to sym-link to them from a directory in the executable path for 
> easier execution of the definitive scripts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)