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

stack commented on HBASE-7119:
------------------------------

In trunk we have a new class named JVM (which we could add to 0.94 too) that is 
supposed to be the place for JVM specific code.  You might add your isIBM to 
this class since it seems like a method that will be needed in a few places.  
This JVM class already has some ibm checking code which you might learn from or 
have use your new isIBM method.  Thanks Li.
                
> org.apache.hadoop.hbase.io.TestHeapSize failed with testNativeSizes unit test
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-7119
>                 URL: https://issues.apache.org/jira/browse/HBASE-7119
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.90.4, 0.90.5, 0.92.0, 0.94.0
>         Environment: RHEL 5.3, open JDK 1.6
>            Reporter: Li Ping Zhang
>            Assignee: Li Ping Zhang
>              Labels: patch
>         Attachments: HBASE-7119-0.94.patch, HBASE-7119-trunk.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Running org.apache.hadoop.hbase.io.TestHeapSize
>       Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.068 
> sec <<< FAILURE!
>  testNativeSizes(org.apache.hadoop.hbase.io.TestHeapSize)  Time elapsed: 0.01 
> sec  <<< FAILURE!
>  junit.framework.AssertionFailedError: expected:<64> but was:<56>
>          at junit.framework.Assert.fail(Assert.java:47)
>          at junit.framework.Assert.failNotEquals(Assert.java:283)
>          at junit.framework.Assert.assertEquals(Assert.java:64)
>          at junit.framework.Assert.assertEquals(Assert.java:130)
>          at junit.framework.Assert.assertEquals(Assert.java:136)
>          at 
> org.apache.hadoop.hbase.io.TestHeapSize.testNativeSizes(TestHeapSize.java:75)
>  

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