java.lang.AssertionError: expected:<3> but was:<1>

GitHub | wildfly-ci | 2 years ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    GitHub comment 8227#145041717

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

    GitHub comment 8227#145041924

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

    GitHub comment 8088#139365582

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

    Automated exception search integrated into your IDE

  5. 0

    GitHub comment 8697#184929116

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

    Root Cause Analysis

    1. java.lang.AssertionError

      expected:<3> but was:<1>

      at org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase.failover()
    2. org.jboss.as
      StatefulFailoverTestCase.jmsConnectionFactoryFailover
      1. org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase.failover(StatefulFailoverTestCase.java:192)
      2. org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase.jmsConnectionFactoryFailover(StatefulFailoverTestCase.java:169)
      2 frames