java.lang.AssertionError: Waited 70 seconds instead an expected 40 seconds wait expected [true] but found [false]

DataStax JIRA | Joaquin Casares | 3 years ago
  1. 0

    https://github.com/joaquincasares/java-driver/commit/a2a3f8890fc32ce4009c7889c90f34eccee48c14 This is unlike the issues that we've had before. Since the last issue was patched everything was working fine, aside from the race conditions that would last at most a few seconds. This new issue is that the waitFor* code can take as long as 250+ seconds before a node comes online. A 200 second delay handled a large number of cases, yet a 250 second delay handles all but typically 1 or 2. This also impacts the overall time it takes for tests to complete. The following issues tend to occur within the Reconnection and Retry Policy tests due to this new increase as well: {CODE} constantReconnectionPolicyTest(com.datastax.driver.core.ReconnectionPolicyTest) Time elapsed: 78.054 sec <<< FAILURE! java.lang.AssertionError: Waited 70 seconds instead an expected 40 seconds wait expected [true] but found [false] at org.testng.Assert.fail(Assert.java:94) at org.testng.Assert.failNotEquals(Assert.java:494) at org.testng.Assert.assertTrue(Assert.java:42) at com.datastax.driver.core.ReconnectionPolicyTest.reconnectionPolicyTest(ReconnectionPolicyTest.java:161) at com.datastax.driver.core.ReconnectionPolicyTest.constantReconnectionPolicyTest(ReconnectionPolicyTest.java:119) exponentialReconnectionPolicyTest(com.datastax.driver.core.ReconnectionPolicyTest) Time elapsed: 70.081 sec <<< FAILURE! java.lang.AssertionError: Waited 62 seconds instead an expected 30 seconds wait expected [true] but found [false] at org.testng.Assert.fail(Assert.java:94) at org.testng.Assert.failNotEquals(Assert.java:494) at org.testng.Assert.assertTrue(Assert.java:42) at com.datastax.driver.core.ReconnectionPolicyTest.reconnectionPolicyTest(ReconnectionPolicyTest.java:161) at com.datastax.driver.core.ReconnectionPolicyTest.exponentialReconnectionPolicyTest(ReconnectionPolicyTest.java:82) defaultLoggingPolicy(com.datastax.driver.core.RetryPolicyTest) Time elapsed: 430.156 sec <<< FAILURE! java.lang.IllegalStateException: 127.0.1.2 is not DOWN after 250s at com.datastax.driver.core.TestUtils.waitFor(TestUtils.java:337) at com.datastax.driver.core.TestUtils.waitForDownWithWait(TestUtils.java:275) at com.datastax.driver.core.RetryPolicyTest.defaultPolicyTest(RetryPolicyTest.java:219) at com.datastax.driver.core.RetryPolicyTest.defaultLoggingPolicy(RetryPolicyTest.java:76) {CODE}

    DataStax JIRA | 3 years ago | Joaquin Casares
    java.lang.AssertionError: Waited 70 seconds instead an expected 40 seconds wait expected [true] but found [false]
  2. 0

    https://github.com/joaquincasares/java-driver/commit/a2a3f8890fc32ce4009c7889c90f34eccee48c14 This is unlike the issues that we've had before. Since the last issue was patched everything was working fine, aside from the race conditions that would last at most a few seconds. This new issue is that the waitFor* code can take as long as 250+ seconds before a node comes online. A 200 second delay handled a large number of cases, yet a 250 second delay handles all but typically 1 or 2. This also impacts the overall time it takes for tests to complete. The following issues tend to occur within the Reconnection and Retry Policy tests due to this new increase as well: {CODE} constantReconnectionPolicyTest(com.datastax.driver.core.ReconnectionPolicyTest) Time elapsed: 78.054 sec <<< FAILURE! java.lang.AssertionError: Waited 70 seconds instead an expected 40 seconds wait expected [true] but found [false] at org.testng.Assert.fail(Assert.java:94) at org.testng.Assert.failNotEquals(Assert.java:494) at org.testng.Assert.assertTrue(Assert.java:42) at com.datastax.driver.core.ReconnectionPolicyTest.reconnectionPolicyTest(ReconnectionPolicyTest.java:161) at com.datastax.driver.core.ReconnectionPolicyTest.constantReconnectionPolicyTest(ReconnectionPolicyTest.java:119) exponentialReconnectionPolicyTest(com.datastax.driver.core.ReconnectionPolicyTest) Time elapsed: 70.081 sec <<< FAILURE! java.lang.AssertionError: Waited 62 seconds instead an expected 30 seconds wait expected [true] but found [false] at org.testng.Assert.fail(Assert.java:94) at org.testng.Assert.failNotEquals(Assert.java:494) at org.testng.Assert.assertTrue(Assert.java:42) at com.datastax.driver.core.ReconnectionPolicyTest.reconnectionPolicyTest(ReconnectionPolicyTest.java:161) at com.datastax.driver.core.ReconnectionPolicyTest.exponentialReconnectionPolicyTest(ReconnectionPolicyTest.java:82) defaultLoggingPolicy(com.datastax.driver.core.RetryPolicyTest) Time elapsed: 430.156 sec <<< FAILURE! java.lang.IllegalStateException: 127.0.1.2 is not DOWN after 250s at com.datastax.driver.core.TestUtils.waitFor(TestUtils.java:337) at com.datastax.driver.core.TestUtils.waitForDownWithWait(TestUtils.java:275) at com.datastax.driver.core.RetryPolicyTest.defaultPolicyTest(RetryPolicyTest.java:219) at com.datastax.driver.core.RetryPolicyTest.defaultLoggingPolicy(RetryPolicyTest.java:76) {CODE}

    DataStax JIRA | 3 years ago | Joaquin Casares
    java.lang.AssertionError: Waited 70 seconds instead an expected 40 seconds wait expected [true] but found [false]
  3. 0

    Unit test verifying Message Directory structure fails on Windows 8

    GitHub | 3 years ago | markusgud
    java.lang.AssertionError: U:\tmp\9908_976098897\AP_1000006\9908_81001709 != 9908_976098897/AP_1000006/9908_81001709 expected [true] but found [false]
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Full run through

    GitHub | 2 years ago | aajenkins
    java.lang.AssertionError: Baseline WebSDK Omniture event verification failed expected [true] but found [false]
  6. 0

    Full run through for Dave

    GitHub | 2 years ago | aajenkins
    java.lang.AssertionError: Baseline WebSDK Omniture event verification failed expected [true] but found [false]

    6 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.AssertionError

      Waited 70 seconds instead an expected 40 seconds wait expected [true] but found [false]

      at org.testng.Assert.fail()
    2. TestNG
      Assert.assertTrue
      1. org.testng.Assert.fail(Assert.java:94)
      2. org.testng.Assert.failNotEquals(Assert.java:494)
      3. org.testng.Assert.assertTrue(Assert.java:42)
      3 frames
    3. DataStax Java Driver for Apache Cassandra - Core
      ReconnectionPolicyTest.constantReconnectionPolicyTest
      1. com.datastax.driver.core.ReconnectionPolicyTest.reconnectionPolicyTest(ReconnectionPolicyTest.java:161)
      2. com.datastax.driver.core.ReconnectionPolicyTest.constantReconnectionPolicyTest(ReconnectionPolicyTest.java:119)
      2 frames