java.lang.AssertionError: expected:<200> but was:<500>

GitHub | wildfly-ci | 1 year ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    GitHub comment 8697#184929116

    GitHub | 1 year ago | wildfly-ci
    java.lang.AssertionError: expected:<200> but was:<500>
  2. 0

    GitHub comment 8172#142350651

    GitHub | 1 year ago | wildfly-ci
    java.lang.AssertionError: expected:<13> but was:<1>
  3. 0

    GitHub comment 8070#139089326

    GitHub | 1 year ago | wildfly-ci
    java.lang.AssertionError: expected:<9> but was:<1>
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    GitHub comment 8227#145041717

    GitHub | 1 year ago | wildfly-ci
    java.lang.AssertionError: expected:<3> but was:<1>
  6. 0

    GitHub comment 8227#145041924

    GitHub | 1 year ago | wildfly-ci
    java.lang.AssertionError: expected:<3> but was:<1>

    Root Cause Analysis

    1. java.lang.AssertionError

      expected:<200> but was:<500>

      at org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase.queryCount()
    2. org.jboss.as
      CdiFailoverTestCase.testGracefulUndeployFailover
      1. org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase.queryCount(CdiFailoverTestCase.java:169)
      2. org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase.testFailover(CdiFailoverTestCase.java:133)
      3. org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase.testGracefulUndeployFailover(CdiFailoverTestCase.java:123)
      3 frames