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 ewencp
, 1 year ago
expected:<1> but was:<0>
via GitHub by hasancelik
, 1 year ago
expected:<0> but was:<1000>
via GitHub by Frank-Bradley
, 2 years ago
i: 0 expected: but was:
via Google Groups by Peter Firmstone, 9 months ago
expected:<0> but was:<3>
via Google Groups by Rajini Sivaram, 3 weeks ago
expected:<5> but was:<1>
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)
java.lang.AssertionError: expected:<1> but was:<0>	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 io.confluent.connect.elasticsearch.BulkProcessorTest.testBatchFailure(BulkProcessorTest.java:141)