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

Hadoop QA commented on HBASE-6823:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12551430/hbase-6823_v2-trunk.patch
  against trunk revision .

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

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

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

    {color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 
85 warning messages.

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

    {color:red}-1 findbugs{color}.  The patch appears to introduce 3 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:red}-1 core tests{color}.  The patch failed these unit tests:
                       
org.apache.hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithAbort

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3188//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3188//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3188//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3188//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3188//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3188//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3188//console

This message is automatically generated.
                
> [WINDOWS] TestSplitTransaction fails due to the Log handle not released by a 
> call to DaughterOpener.start()
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-6823
>                 URL: https://issues.apache.org/jira/browse/HBASE-6823
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.94.3, 0.96.0
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>              Labels: windows
>             Fix For: 0.96.0
>
>         Attachments: hbase-6823_v1-0.94.patch, hbase-6823_v1-trunk.patch, 
> hbase-6823_v2-0.94.patch, hbase-6823_v2-trunk.patch
>
>
> There are two unit test cases in HBase RegionServer test failed in the clean 
> up stage that failed to delete the files/folders created in the test. 
> testWholesomeSplit(org.apache.hadoop.hbase.regionserver.TestSplitTransaction):
>  Failed delete of ./target/test-
> data/1c386abc-f159-492e-b21f-e89fab24d85b/org.apache.hadoop.hbase.regionserver.TestSplitTransaction/table/a588d813fd26280c2b42e93565ed960c
> testRollback(org.apache.hadoop.hbase.regionserver.TestSplitTransaction): 
> Failed delete of ./target/test-data/6
> 1a1a14b-0cc9-4dd6-93fd-4dc021e2bfcc/org.apache.hadoop.hbase.regionserver.TestSplitTransaction/table/8090abc89528461fa284288c257662cd
> The root cause is triggered by ta call to the DaughterOpener.start() in 
> \src\hbase\src\main\java\org\apache\hadoop\hbase\regionserver\SplitTransactopn.Java
>  (openDaughters() function). It left handles to the splited folder/file and 
> causing deleting of the file/folder failed in the Windows OS.
> Windows does not allow to delete a file, while there are open file handlers.

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