[
https://issues.apache.org/jira/browse/GEODE-8176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144864#comment-17144864
]
Alberto Bustamante Reyes commented on GEODE-8176:
-------------------------------------------------
I think the problem is a race condition between the ping updating the
ClientHealthMonitor and the test case checking the ClientHealthMonitor content.
If I introduce a delay in the message before updating the ClientHealthMonitor,
the test case fails as it failed in the reported CI executions.
So Im introducing a wait in the test case to avoid this situation. Hopefully
this will solve the issue, and also GEODE-8245.
https://github.com/apache/geode/pull/5303
> CI Failure: ClientServerMiscBCDUnitTest > testPingWrongServer[1]
> -----------------------------------------------------------------
>
> Key: GEODE-8176
> URL: https://issues.apache.org/jira/browse/GEODE-8176
> Project: Geode
> Issue Type: Bug
> Reporter: Donal Evans
> Assignee: Alberto Bustamante Reyes
> Priority: Major
> Labels: flaky
>
> Failed in
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK8/builds/192#A
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest >
> testPingWrongServer[1] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscDUnitTestBase$$Lambda$310/201549247.run
> in VM 3 running on Host c0a964e32781 with 5 VMs
> Caused by:
> org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e>
> {noformat}
> I ran the test 200 times locally with no failure, so this is possibly just a
> blip.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
