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 hadoop-hdfs-dev by Apache Jenkins Server, 1 year ago
via ranger-dev by Sitaraman Vilayannur, 1 year ago
expected:<0> but was:<1>
via nabble.com by Unknown author, 2 years ago
via GitHub by ejona86
, 2 years ago
expected:<0> but was:<1>
via ranger-dev by Ashish Singh, 1 year ago
expected:<0> but was:<1>
via ranger-dev by Gautam Borad, 1 year ago
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: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 org.apache.hadoop.hdfs.server.blockmanagement.TestPendingReplication.testPendingAndInvalidate(TestPendingReplication.java:293)