[ACCUMULO-4417] JUnit timeout rule not firing under circumstances of ACCUMULO-4416

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Cannot Reproduce
• Affects Version/s: 1.7.1
• Component/s: test
• Assignee: Josh Elser
• Reporter: Josh Elser
• Created: 19/Aug/16 22:39
• Updated: 23/Apr/19 23:21
• Resolved: 23/Apr/19 23:21

Description

Not a pure-apache release stacktrace:

java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at org.apache.accumulo.core.util.UtilWaitThread.sleep(UtilWaitThread.java:27)
at org.apache.accumulo.core.client.impl.ServerClient.executeRaw(ServerClient.java:102)
at org.apache.accumulo.core.client.impl.ServerClient.execute(ServerClient.java:61)
at org.apache.accumulo.core.client.impl.ConnectorImpl.<init>(ConnectorImpl.java:67)
at org.apache.accumulo.core.client.ZooKeeperInstance.getConnector(ZooKeeperInstance.java:248)
at org.apache.accumulo.minicluster.impl.MiniAccumuloClusterImpl.getConnector(MiniAccumuloClusterImpl.java:722)
at org.apache.accumulo.harness.SharedMiniClusterIT.startMiniClusterWithConfig(SharedMiniClusterIT.java:108)
at org.apache.accumulo.harness.SharedMiniClusterIT.startMiniCluster(SharedMiniClusterIT.java:65)
at org.apache.accumulo.test.replication.StatusCombinerMacIT.setup(StatusCombinerMacIT.java:61)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
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.RunBefores.evaluate(RunBefores.java:24)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)

This test has been sitting like this for ~18hrs but the configuration should have killed it after 6 minutes. Need to figure out if this is because of our UtilWaitThread or similar (e.g. eating interrupts).