[
https://issues.apache.org/jira/browse/HBASE-6100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409048#comment-13409048
]
Andrew Purtell commented on HBASE-6100:
---------------------------------------
TestZooKeeper.testClientSessionExpired and
TestServerCustomProtocol.testSingleMethod pass on our privte Hudson, and
locally, so I think this is some evidence toward those being test code issues.
On our private Hudson, against Hadoop 2.0.1-SNAPSHOT, we see these failures:
org.apache.hadoop.hbase.TestLocalHBaseCluster.testLocalHBaseCluster
org.apache.hadoop.hbase.client.TestMetaMigrationRemovingHTD.org.apache.hadoop.hbase.client.TestMetaMigrationRemovingHTD
org.apache.hadoop.hbase.mapreduce.TestImportExport.testSimpleCase
org.apache.hadoop.hbase.mapreduce.TestImportExport.testWithDeletes
org.apache.hadoop.hbase.regionserver.wal.TestLogRolling.testLogRollOnPipelineRestart
TestLogRolling.testLogRollOnPipelineRestart is covered by HBASE-5995. Maybe
this needs HDFS level tinkering.
The TestLocalHBaseCluster.testLocalHBaseCluster failure is some weird recursion
in FileSystem.get leading to a StackOverflowError, so this particular failure
instance may be specific to Hadoop 2.
I have some new team members needing training so part of that will be digging
into these failures "real soon now".
> Fix the frequent testcase failures in 0.94 from build no #209
> -------------------------------------------------------------
>
> Key: HBASE-6100
> URL: https://issues.apache.org/jira/browse/HBASE-6100
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: ramkrishna.s.vasudevan
> Fix For: 0.94.2
>
>
> Fix the flaky tests in 0.94 branch after #209. Many test cases like the
> org.apache.hadoop.hbase.TestLocalHBaseCluster.testLocalHBaseCluster
> org.apache.hadoop.hbase.TestZooKeeper.testClientSessionExpired
> org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol.testSingleMethod
> are failing frequently.
--
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
