Kamilla Aslami created GEODE-9448:
-------------------------------------
Summary: CI Failure: MemberMXBeanDistributedTest.testBucketCount
failed with ConditionTimeoutException caused by TimeoutException
Key: GEODE-9448
URL: https://issues.apache.org/jira/browse/GEODE-9448
Project: Geode
Issue Type: Bug
Components: jmx, tests
Reporter: Kamilla Aslami
This failure is similar to GEODE-8191 but the stack trace looks a bit different:
{noformat}
org.apache.geode.management.MemberMXBeanDistributedTest > testBucketCount FAILED
org.awaitility.core.ConditionTimeoutException: Assertion condition defined
as a lambda expression in
org.apache.geode.management.MemberMXBeanDistributedTest expected:<[400]0> but
was:<[375]0> within 5 minutes.
at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:166)
at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:939)
at
org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
at
org.apache.geode.management.MemberMXBeanDistributedTest.testBucketCount(MemberMXBeanDistributedTest.java:108)
Caused by:
java.util.concurrent.TimeoutException
at java.util.concurrent.FutureTask.get(FutureTask.java:204)
at
org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:101)
at
org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:81)
at
org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:102)
... 5 more{noformat}
I noticed that in the last failure reported on GEODE-8191 ([run
#26|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/distributed-test-openjdk8/builds/26]),
the version of Awaitility was 4.0.3. In this failure, the version is 4.1.0, so
this might be the reason why the stack traces are different.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
