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

Hadoop QA commented on HBASE-10203:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12619409/10203-v1.txt
  against trunk revision .
  ATTACHMENT ID: 12619409

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

    {color:green}+1 tests included{color}.  The patch appears to include 6 new 
or modified tests.

    {color:green}+1 hadoop1.0{color}.  The patch compiles against the hadoop 
1.0 profile.

    {color:green}+1 hadoop1.1{color}.  The patch compiles against the hadoop 
1.1 profile.

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

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

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) 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:red}-1 site{color}.  The patch appears to cause mvn site goal to 
fail.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

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

This message is automatically generated.

> Separate testLogRollOnPipelineRestart out of TestLogRolling
> -----------------------------------------------------------
>
>                 Key: HBASE-10203
>                 URL: https://issues.apache.org/jira/browse/HBASE-10203
>             Project: HBase
>          Issue Type: Test
>            Reporter: Ted Yu
>            Priority: Minor
>         Attachments: 10203-v1.txt
>
>
> From 
> https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/16/testReport/org.apache.hadoop.hbase.regionserver.wal/TestLogRolling/
>  :
> {code}
> testCompactionRecordDoesntBlockRolling        30 sec  Passed
> testLogRollOnDatanodeDeath    3 min 19 sec    Passed
> testLogRollOnPipelineRestart  6 min 16 sec    Passed
> testLogRolling        4 min 27 sec    Passed
> {code}
> We can see that testLogRollOnPipelineRestart took almost as long as the other 
> tests combined.
> This JIRA separates testLogRollOnPipelineRestart out of TestLogRolling



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Reply via email to