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

Hadoop QA commented on HBASE-6965:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12549204/HBASE-6965.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: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 
82 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 9 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.catalog.TestMetaReaderEditor

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

This message is automatically generated.
                
> Generic MXBean Utility class to support all JDK vendors
> -------------------------------------------------------
>
>                 Key: HBASE-6965
>                 URL: https://issues.apache.org/jira/browse/HBASE-6965
>             Project: HBase
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 0.94.1
>            Reporter: Kumar Ravi
>            Assignee: Kumar Ravi
>              Labels: patch
>             Fix For: 0.94.3
>
>         Attachments: HBASE-6965.patch
>
>
> This issue is related to JIRA 
> https://issues.apache.org/jira/browse/HBASE-6945. This issue is opened to 
> propose the use of a newly created generic 
> org.apache.hadoop.hbase.util.OSMXBean class that can be used by other 
> classes. JIRA HBASE-6945 contains a patch for the class 
> org.apache.hadoop.hbase.ResourceChecker that uses OSMXBean. With the 
> inclusion of this new class, HBase can be built and become functional with 
> JDKs and JREs other than what is provided by Oracle.
>  This class uses reflection to determine the JVM vendor (Sun, IBM) and the 
> platform (Linux or Windows), and contains other methods that return the OS 
> properties - 1. Number of Open File descriptors;  2. Maximum number of File 
> Descriptors.
>  This class compiles without any problems with IBM JDK 7, OpenJDK 6 as well 
> as Oracle JDK 6. Junit tests (runDevTests category) completed without any 
> failures or errors when tested on all the three JDKs.The builds and tests 
> were attempted on branch hbase-0.94 Revision 1396305.

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