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

    This exception could rise due to a connection timeout.

Solutions on the web

via xuebuyuan.com by Unknown author, 2 years ago
expected:<9> but was:<2147483647>      at junit.framework.Assert.fail(Assert.java:47)
via grokbase.com by Unknown author, 1 year ago
via grokbase.com by Unknown author, 2 years ago
via nabble.com by Unknown author, 1 year ago
expected:<SUCCESSbut was:<FAILURE>         at junit.framework.Assert.fail(Assert.java:47)
via apache.org by Unknown author, 1 year ago
expected:<0> but was:<1> at junit.framework.Assert.fail(Assert.java:47)
via hortonworks.com by Unknown author, 2 years ago
expected:<0> but was:<1> at junit.framework.Assert.fail(Assert.java:47)
junit.framework.AssertionFailedError: expected:<SUCCESS> but was:<FAILURE>
    at junit.framework.Assert.fail(Assert.java:47)	at junit.framework.Assert.failNotEquals(Assert.java:282)	at junit.framework.Assert.assertEquals(Assert.java:64)	at junit.framework.Assert.assertEquals(Assert.java:71)	at hudson.scm.SubversionSCMTest.testTaggingPermission(SubversionSCMTest.java:38)