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

Solutions on the web

via GitHub by ejona86
, 1 year ago
expected:<3> but was:<2>
via GitHub by ejona86
, 1 year ago
expected:<3> but was:<0>
via GitHub by ejona86
, 1 year ago
expected:<3> but was:<0>
via GitHub by ejona86
, 1 year ago
expected:<3> but was:<0>
via GitHub by ejona86
, 1 year ago
expected:<3> but was:<0>
java.lang.AssertionError: expected:<3> but was:<2>	at org.junit.Assert.fail(Assert.java:88)	at org.junit.Assert.failNotEquals(Assert.java:743)	at org.junit.Assert.assertEquals(Assert.java:118)	at org.junit.Assert.assertEquals(Assert.java:555)	at org.junit.Assert.assertEquals(Assert.java:542)	at io.grpc.testing.integration.CascadingTest.testCascadingCancellationViaMethodTimeout(CascadingTest.java:161)