[
https://issues.apache.org/jira/browse/HBASE-8392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13638708#comment-13638708
]
Elliott Clark commented on HBASE-8392:
--------------------------------------
We should just delete all the tests in org.apache.hbase.metrics inside of
hbase-server. These were all left over tests for classes that hbase created to
interact with hadoop's older metrics system. There's no mention of any class
that's under test in the flakey tests, so keeping them and fixing them provides
little to no value.
The old metrics system in hadoop branch-2+ hasn't really gotten much in the way
of attention since it has been deprecated; that could explain why this is
flakey in hadoop 2.
> TestMetricMBeanBase#testGetAttribute is flakey under hadoop2 profile
> --------------------------------------------------------------------
>
> Key: HBASE-8392
> URL: https://issues.apache.org/jira/browse/HBASE-8392
> Project: HBase
> Issue Type: Sub-task
> Components: hadoop2, metrics, test
> Affects Versions: 0.98.0, 0.95.0
> Reporter: Jonathan Hsieh
> Fix For: 0.95.1
>
>
> This specific small unit tests flakes out occasionally and blocks the medium
> and large tests from running.
> Here's an error trace:
> {code}
> Error Message
> expected:<2.0> but was:<0.125>
> Stacktrace
> junit.framework.AssertionFailedError: expected:<2.0> but was:<0.125>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:120)
> at junit.framework.Assert.assertEquals(Assert.java:129)
> at junit.framework.TestCase.assertEquals(TestCase.java:288)
> at
> org.apache.hadoop.hbase.metrics.TestMetricsMBeanBase.testGetAttribute(TestMetricsMBeanBase.java:93)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.junit.runners.Suite.runChild(Suite.java:127)
> at org.junit.runners.Suite.runChild(Suite.java:26)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> {code}
> [~eclark] took a quick look and will chime in on this.
--
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
