java.lang.AssertionError: expected:<LOCK_FAILURE> but was:<FOUND>

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

,
Expert tip

Check your pattern declaration or check your assert declaration.

Solutions on the web

via GitHub by anuraaga
, 7 months ago
expected:<3> but was:<2>
via GitHub by phax
, 2 years ago
expected:<sha512> but was:<null>
via Google Groups by Peter Firmstone, 4 months ago
expected:<0> but was:<3>
java.lang.AssertionError: expected:<LOCK_FAILURE> but was:<FOUND>
at org.junit.Assert.fail(Assert.java:91)
at org.junit.Assert.failNotEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:126)
at org.junit.Assert.assertEquals(Assert.java:145)
at org.kuali.kits.kms.repository.test.BatchProcessorTest.testAsikLocking(BatchProcessorTest.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)

Users with the same issue

19 times, 4 days ago
2 times, 6 months ago
Once, 4 months ago
Once, 10 months ago
Once, 8 months ago

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.