[
https://issues.apache.org/jira/browse/HBASE-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13139153#comment-13139153
]
Hadoop QA commented on HBASE-4701:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12501430/4701.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
-1 javadoc. The javadoc tool appears to have generated -166 warning
messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 1 new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.master.TestDistributedLogSplitting
org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/96//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/96//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/96//console
This message is automatically generated.
> TestMasterObserver fails up on jenkins
> --------------------------------------
>
> Key: HBASE-4701
> URL: https://issues.apache.org/jira/browse/HBASE-4701
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Attachments: 4701.txt
>
>
> This fails for various reasons from not being able to find the region we're
> to move in master list of regions to fails because of 'too many open files'
> (I believe Giri has fixed this on some of the hadoop nodes but looks like not
> all).
> Here is a refactor around the move w/ asserts, more logging, use of updated
> apis, and with check that what we're moving has a server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
