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 Frank-Bradley
, 2 years ago
i: 0 expected: but was:
via Google Groups by Peter Firmstone, 6 months ago
expected:<0> but was:<3>
via GitHub by hasancelik
, 1 year ago
expected:<0> but was:<1000>
via osdir.com by Unknown author, 2 years ago
There should be one document because overwrite=true expected:<1> but was:<0> at __randomizedtesting.SeedInfo.seed([573006190B77DDC9:DF6439C3A58BB031]:0)
via Google Groups by Michael Portuesi, 7 months ago
@Implementation method mismatch: public void > com.xtremelabs.robolectric.shadows.ShadowCameraSize.__constructor__(int,int ) > doesn't match a real method expected:<0> but was:<1>
java.lang.AssertionError: expected:<0> but was:<1>	at org.junit.Assert.fail(Assert.java:88)	at org.junit.Assert.failNotEquals(Assert.java:834)	at org.junit.Assert.assertEquals(Assert.java:645)	at org.junit.Assert.assertEquals(Assert.java:631)	at com.hazelcast.internal.partition.MigrationAwareServiceEventTest$1.run(MigrationAwareServiceEventTest.java:70)	at com.hazelcast.test.HazelcastTestSupport.assertTrueEventually(HazelcastTestSupport.java:901)	at com.hazelcast.test.HazelcastTestSupport.assertTrueEventually(HazelcastTestSupport.java:915)	at com.hazelcast.internal.partition.MigrationAwareServiceEventTest.migrationCommitEvents_shouldBeEqual_onSource_and_onDestination(MigrationAwareServiceEventTest.java:81)