Jens Deppe created GEODE-5373:
---------------------------------
Summary: GMSHealthMonitorJUnitTest.testRemoveMemberCalled fails on
Windows
Key: GEODE-5373
URL: https://issues.apache.org/jira/browse/GEODE-5373
Project: Geode
Issue Type: Bug
Components: membership
Reporter: Jens Deppe
When run in isolation this test does not fail, but as soon as it is run as part
of the whole class it fails as follows:
{noformat}
testRemoveMemberCalled starting
[info 2018/07/03 08:14:18.670 PDT <Geode Failure Detection Server thread 0>
tid=26] Started failure detection server thread on
blue-leader/169.254.80.90:29514.
[info 2018/07/03 08:14:19.170 PDT <main> tid=1] received suspect message from
blue-leader(7036:locator)<ec>:8888 for blue-leader(7036:locator)<ec>:8889: Not
Responding
[info 2018/07/03 08:14:19.170 PDT <Geode Failure Detection thread 1> tid=28]
Performing final check for suspect member blue-leader(7036:locator)<ec>:8889
reason=Not Responding
[info 2018/07/03 08:14:19.170 PDT <Geode Failure Detection thread 1> tid=28]
Unable to locate failure detection port - requesting a heartbeat
[info 2018/07/03 08:14:19.186 PDT <Geode Failure Detection Scheduler> tid=25]
--->>> memberTimeStamps.put: blue-leader(7036)<ec>:8890 1530630859186
[info 2018/07/03 08:14:20.185 PDT <Geode Failure Detection Scheduler> tid=25]
--->>> memberTimeStamps.put: blue-leader(7036:locator)<ec>:8889 1530630860185
[info 2018/07/03 08:14:20.185 PDT <Geode Failure Detection thread 1> tid=28]
--->>> member: blue-leader(7036:locator)<ec>:8889 ts: 1530630860185 startTime:
1530630859170
[info 2018/07/03 08:14:20.185 PDT <Geode Failure Detection thread 1> tid=28]
Final check failed but detected recent message traffic for suspect member
blue-leader(7036:locator)<ec>:8889
[info 2018/07/03 08:14:20.185 PDT <Geode Failure Detection thread 1> tid=28]
Final check passed for suspect member blue-leader(7036:locator)<ec>:8889
[info 2018/07/03 08:14:22.195 PDT <main> tid=1] GMSHealthMonitor server socket
is closed in stopServices().
[info 2018/07/03 08:14:22.195 PDT <Geode Failure Detection Server thread 0>
tid=26] GMSHealthMonitor server thread exiting
[info 2018/07/03 08:14:22.195 PDT <main> tid=1] GMSHealthMonitor
serverSocketExecutor is terminated
org.awaitility.core.ConditionTimeoutException: Condition with alias 'waiting
for remove(member) to be invoked' didn't complete within 3000 milliseconds
because condition with alias waiting for remove(member) to be invoked defined
as a lambda expression in
org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitorJUnitTest
Wanted but not invoked:
joinLeave.remove(
<any
org.apache.geode.distributed.internal.membership.InternalDistributedMember>,
<any java.lang.String>
);
-> at
org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitorJUnitTest.lambda$testRemoveMemberCalled$0(GMSHealthMonitorJUnitTest.java:386)
However, there were exactly 3 interactions with this mock:
joinLeave.isMemberLeaving(
blue-leader(7036:locator)<ec>:8889
);
-> at
org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.inlineCheckIfAvailable(GMSHealthMonitor.java:1278)
joinLeave.isMemberLeaving(
blue-leader(7036:locator)<ec>:8889
);
-> at
org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.initiateSuspicion(GMSHealthMonitor.java:437)
joinLeave.getMemberID();
-> at
org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.sendSuspectRequest(GMSHealthMonitor.java:1384)
.
at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:104)
at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:117)
at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:809)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:648)
at
org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitorJUnitTest.testRemoveMemberCalled(GMSHealthMonitorJUnitTest.java:385)
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:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
at
com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
at
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
Process finished with exit code -1{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
