Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    Expert tip

    Check your pattern declaration or check your assert declaration.

Solutions on the web

via GitHub by wildfly-ci
, 1 year ago
expected:<20030303> but was:<20010101>
via GitHub by wildfly-ci
, 1 year ago
expected:<20030303> but was:<20010101>
via GitHub by wildfly-ci
, 1 year ago
expected:<20030303> but was:<20010101>
via GitHub by wildfly-ci
, 1 year ago
expected:<20030303> but was:<20010101>
via github.com by Unknown author, 2 years ago
via GitHub by wildfly-ci
, 1 year ago
expected:<20030303> but was:<20010101>
java.lang.AssertionError: expected:<20030303> but was:<20010101>	at org.junit.Assert.fail(Assert.java:88)	at org.junit.Assert.failNotEquals(Assert.java:743)