[
https://issues.apache.org/jira/browse/HBASE-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599495#comment-13599495
]
Hadoop QA commented on HBASE-8069:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12573189/HBASE-8069-v0.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: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:red}-1 core tests{color}. The patch failed these unit tests:
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/4766//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4766//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4766//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4766//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4766//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4766//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4766//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4766//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4766//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4766//console
This message is automatically generated.
> TestHLog is dependent on the execution order
> --------------------------------------------
>
> Key: HBASE-8069
> URL: https://issues.apache.org/jira/browse/HBASE-8069
> Project: HBase
> Issue Type: Bug
> Components: test, wal
> Affects Versions: 0.95.0, 0.94.5
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Attachments: HBASE-8069-v0.patch, HBASE-8069-v0.patch
>
>
> Changing the execution order of the tests, TestHLog show up as failing
> {code}<runOrder>alphabetical</runOrder>{code}
> testAppendClose() changes the DFS cluster of the test (set globally) so the
> tests executed after has the new DFS. Trying to start a new mini cluster for
> every test @Before seems to solve the problem.
> {code}
> testSplit(org.apache.hadoop.hbase.regionserver.wal.TestHLog): 3 exceptions
> [org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.hdfs.server.namenode.LeaseExpiredException):
> No lease on
> /user/th30z/hbase/TestHLog/21985ea121a1d65fa82d90d521be7313/recovered.edits/0000000000000000001.temp
> File is not open for writing. Holder DFSClient_NONMAPREDUCE_1044150136_583
> does not have any open files.
> {code}
> Looking at testSplit() the failure seems to be in logSplitter.splitLog(),
> OutputSink.finishWritingAndClose() is not able to close the files and rethrow
> the exception.
--
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
