Uploaded image for project: 'Geode'
  1. Geode
  2. GEODE-7657

Container not updated in Tomcat8CachingClientServerTest > containersShouldShareDataRemovals

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • http session
    • None

    Description

      CI failure: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1455

      Test results: http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0169/test-results/distributedTest/1578353528/classes/org.apache.geode.session.tests.Tomcat8CachingClientServerTest.html#containersShouldShareDataRemovals

      The logs show this explanation just before the awaitility loop:

      [info 2020/01/06 21:44:06.750 GMT <Test worker> tid=0x19] verifying container 1 for expected value of Foo for key value_testSessionRemove, but gets response value of . Waiting for update from server.

      This is followed by five minutes of repetitions of:

      [info 2020/01/06 21:44:06.886 GMT <awaitility-thread> tid=0x169] client gets response value of
      
      

      The value appears to be either null or empty.

      Stack trace starts with:

      org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in org.apache.geode.session.tests.CargoTestBase was not fulfilled within 300 seconds. at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145) at org.awaitility.core.CallableCondition.await(CallableCondition.java:79) at org.awaitility.core.CallableCondition.await(CallableCondition.java:27) at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902) at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:860) at org.apache.geode.session.tests.CargoTestBase.getKeyValueDataOnAllClients(CargoTestBase.java:145) at org.apache.geode.session.tests.CargoTestBase.containersShouldShareDataRemovals(CargoTestBase.java:344)

      When fixing this problem, please also update the awaitility loop to give a more informative failure message, perhaps by using `await().untilAsserted()`.

      Attachments

        Activity

          People

            Unassigned Unassigned
            demery Dale Emery
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: