java.lang.AssertionError: expected:<20030303> but was:<20010101>

GitHub | wildfly-ci | 8 months ago
  1. 0

    GitHub comment 8227#145041717

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

    GitHub comment 8227#145041924

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

    GitHub comment 8794#209486432

    GitHub | 8 months ago | wildfly-ci
    java.lang.AssertionError: expected:<20030303> but was:<20010101>
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    GitHub comment 8794#209489963

    GitHub | 8 months ago | wildfly-ci
    java.lang.AssertionError: expected:<20030303> but was:<20010101>
  6. 0

    GitHub comment 7982#138597918

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

    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

      expected:<20030303> but was:<20010101>

      at org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase.nestedBeanFailover()
    2. org.jboss.as
      StatefulFailoverTestCase.nestedBeanFailover
      1. org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase.nestedBeanFailover(StatefulFailoverTestCase.java:285)
      1 frame