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.

  2. ,

    My guess is there is some kind of static state in the code being tested or in the test itself, so the tests aren't isolated. Adding the test changes the test order. In any case, your best course of action is to use the debugger to see why the tests fail.

Solutions on the web

via GitHub by stefanfeyer
, 1 year ago
Obsolete keys found in language properties file: [Remember_these_entry_types?] 1. CHECK IF THE KEY IS REALLY NOT USED ANYMORE 2. REMOVE THESE FROM THE ENGLISH LANGUAGE FILE 3. EXECUTE: gradlew localizationUpdate expected:<[]> but was:<[Remember_these_entry_types?]>
via GitHub by yurishkuro
, 11 months ago
expected:<0> but was:<1>
via GitHub by yurishkuro
, 11 months ago
expected:<0> but was:<1>
via hadoop-hdfs-issues by Jimmy Xiang (JIRA), 2 years ago
via hadoop-hdfs-issues by Jimmy Xiang (JIRA), 2 years ago
via hadoop-hdfs-issues by Jimmy Xiang (JIRA), 2 years ago
java.lang.AssertionError: Obsolete keys found in language properties file: [Remember_these_entry_types?] 1. CHECK IF THE KEY IS REALLY NOT USED ANYMORE 2. REMOVE THESE FROM THE ENGLISH LANGUAGE FILE 3. EXECUTE: gradlew localizationUpdate expected:<[]> but was:<[Remember_these_entry_types?]> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:118) at net.sf.jabref.logic.l10n.LocalizationConsistencyTest.findObsoleteLocalizationKeys(LocalizationConsistencyTest.java:153)