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

Hadoop QA commented on HBASE-7120:
----------------------------------

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

    {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:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/4605//console

This message is automatically generated.
                
> hbase-daemon.sh (start) missing necessary check when writing pid and log files
> ------------------------------------------------------------------------------
>
>                 Key: HBASE-7120
>                 URL: https://issues.apache.org/jira/browse/HBASE-7120
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.94.0
>         Environment: RHEL 5.3, open JDK 1.6
>            Reporter: Li Ping Zhang
>            Assignee: Li Ping Zhang
>              Labels: patch
>         Attachments: HBASE-7120-0.94.patch, HBASE-7120-0.94-v1.patch, 
> HBASE-7120-trunk.patch, HBASE-7120-trunk-v1.patch, 
> HBASE-7120-trunk-working.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> $HBASE_HOME/bin/hbase-daemon.sh exit code is Zero, when runing 
> hbase-daemon.sh failed with "start", which doesn’t do required command exit 
> code check, it's better to do necessary check when writing pid and log files. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to