java.lang.AssertionError: expected:<1> but was:<0>

GitHub | ewencp | 8 months ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    GitHub comment 2#229553494

    GitHub | 8 months ago | ewencp
    java.lang.AssertionError: expected:<1> but was:<0>
  2. 0

    GitHub comment 5453#150218665

    GitHub | 1 year ago | hasancelik
    java.lang.AssertionError: expected:<1> but was:<0>
  3. Speed up your debug routine!

    Automated exception search integrated into your IDE

  4. 0

    GitHub comment 6509#149818519

    GitHub | 1 year ago | serkan-ozal
    java.lang.AssertionError: expected:<1> but was:<0>
  5. 0

    GitHub comment 5453#160567760

    GitHub | 1 year ago | hasancelik
    java.lang.AssertionError: expected:<1> but was:<0>

  1. jf-ast 3 times, last 2 weeks ago
  2. treefolk 3 times, last 2 weeks ago
  3. kjhdofjosvs 1 times, last 1 month ago
  4. MoYapro 3 times, last 2 months ago
  5. andyglick 1 times, last 2 months ago
5 more registered users
32 unregistered visitors
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:<1> but was:<0>

    at org.junit.Assert.fail()
  2. JUnit
    Assert.assertEquals
    1. org.junit.Assert.fail(Assert.java:88)
    2. org.junit.Assert.failNotEquals(Assert.java:834)
    3. org.junit.Assert.assertEquals(Assert.java:645)
    4. org.junit.Assert.assertEquals(Assert.java:631)
    4 frames
  3. io.confluent.connect
    BulkProcessorTest.testBatchFailure
    1. io.confluent.connect.elasticsearch.BulkProcessorTest.testBatchFailure(BulkProcessorTest.java:141)
    1 frame