[
https://issues.apache.org/jira/browse/HBASE-8900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715346#comment-13715346
]
stack commented on HBASE-8900:
------------------------------
I am going to remove from trunk too.
Here we have one of those silent failures. If I compare a list of tests that
passed on successful run to those that show on this fail I get this difference:
{code}
durruti:trunk stack$ diff /tmp/bad_trunk.txt /tmp/good_trunk.txt
91a92
> Running org.apache.hadoop.hbase.mapreduce.TestMultiTableInputFormat
159a161
> Running
> org.apache.hadoop.hbase.regionserver.TestRSKilledWhenMasterInitializing
176a179,180
> Running org.apache.hadoop.hbase.regionserver.wal.TestHLogSplitCompressed
> Running org.apache.hadoop.hbase.regionserver.wal.TestLogRollAbort
183,185c187,188
< Running org.apache.hadoop.hbase.replication.TestReplicationKillMasterRS
< Running
org.apache.hadoop.hbase.replication.TestReplicationKillMasterRSCompressed
< Running org.apache.hadoop.hbase.replication.TestReplicationKillSlaveRS
---
> Running org.apache.hadoop.hbase.replication.TestReplicationQueueFailover
> Running
> org.apache.hadoop.hbase.replication.TestReplicationQueueFailoverCompressed
200a204
> Running org.apache.hadoop.hbase.rest.client.TestRemoteAdmin
{code}
TestMultiTableInputFormat has been removed already.
TestReplicationKillMasterRS is likely new since the good run. etc.
TestRSKilledWhenMasterInitializing is in the list. I'm going to remove it for
now until it has been fixed. It is already removed from 0.95. Doing same for
trunk so can get clean builds.
> TestRSKilledWhenMasterInitializing.testCorrectnessWhenMasterFailOver is flakey
> ------------------------------------------------------------------------------
>
> Key: HBASE-8900
> URL: https://issues.apache.org/jira/browse/HBASE-8900
> Project: HBase
> Issue Type: Bug
> Components: test
> Reporter: stack
> Assignee: ramkrishna.s.vasudevan
> Attachments: 8900.txt
>
>
> Failed here:
> https://builds.apache.org/job/hbase-0.95-on-hadoop2/169/testReport/junit/org.apache.hadoop.hbase.regionserver/TestRSKilledWhenMasterInitializing/testCorrectnessWhenMasterFailOver/
> and
> http://54.241.6.143/job/HBase-0.95-Hadoop-2/579/org.apache.hbase$hbase-server/testReport/junit/org.apache.hadoop.hbase.regionserver/TestRSKilledWhenMasterInitializing/org_apache_hadoop_hbase_regionserver_TestRSKilledWhenMasterInitializing/
> {code}
> java.lang.Exception: test timed out after 120000 milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.zookeeper.ZKAssign.blockUntilNoRIT(ZKAssign.java:1002)
> at
> org.apache.hadoop.hbase.regionserver.TestRSKilledWhenMasterInitializing.testCorrectnessWhenMasterFailOver(TestRSKilledWhenMasterInitializing.java:177)
> 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
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
> {code}
> and with this:
> {code}
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.regionserver.TestRSKilledWhenMasterInitializing.tearDownAfterClass(TestRSKilledWhenMasterInitializing.java:83)
> 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
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> 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:439)
> 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:895)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> {code}
--
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
