[ https://issues.apache.org/jira/browse/GEODE-6462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807092#comment-16807092 ]
Helena Bales commented on GEODE-6462: ------------------------------------- Saw this exact failure again in PR pipeline. CI run: [https://concourse.apachegeode-ci.info/builds/52750] Artifacts: [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-3378/test-results/distributedTest/1554145740/] > [CI Failure] LocatorConnectionDUnitTest > testGetAvailableServersWithStats > failed on validateStats > -------------------------------------------------------------------------------------------------- > > Key: GEODE-6462 > URL: https://issues.apache.org/jira/browse/GEODE-6462 > Project: Geode > Issue Type: Test > Components: core > Reporter: Jens Deppe > Priority: Major > Labels: ci > > This seems like a flakey test. > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/443] > The test and the protobuf code has not been updated in a while. This is > probably a flake. > The following is the error thread > {code:java} > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest > > testGetAvailableServersWithStats FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest$$Lambda$37/842046356.run > in VM 0 running on Host 22c25e73171b with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:406) > at > org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:85) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.validateStats(LocatorConnectionDUnitTest.java:234) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.testSocketWithStats(LocatorConnectionDUnitTest.java:127) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.testGetAvailableServersWithStats(LocatorConnectionDUnitTest.java:106) > Caused by: > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest > that uses long, longlong, longlong, longlong, longint, intint expected:<3> > but was:<4> within 300 seconds. > at > org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32) > at > org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902) > at > org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.lambda$validateStats$c7642ca0$1(LocatorConnectionDUnitTest.java:235) > Caused by: > java.lang.AssertionError: expected:<3> but was:<4> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.lambda$null$0(LocatorConnectionDUnitTest.java:238) > {code} > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > [http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-SNAPSHOT.0487/test-results/distributedTest/1551228892/] > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > [http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-SNAPSHOT.0487/test-artifacts/1551228892/distributedtestfiles-OpenJDK8-1.9.0-SNAPSHOT.0487.tgz] -- This message was sent by Atlassian JIRA (v7.6.3#76005)