[hotfix] Disable KryoSerializerConcurrencyCheckInactiveITCase if logg…

…ing level is DEBUG

flink-core/src/test/java/org/apache/flink/api/java/typeutils/runtime/kryo/KryoSerializerConcurrencyCheckInactiveITCase.java

@@ -18,9 +18,12 @@
 
 package org.apache.flink.api.java.typeutils.runtime.kryo;
 
+import org.apache.flink.util.TestLogger;
+
 import org.junit.Test;
 
 import static org.junit.Assert.assertTrue;
+import static org.junit.Assume.assumeFalse;
 
 /**
  * A test that validates that the concurrency checks in the Kryo Serializer
@@ -33,7 +36,7 @@
  * <p><b>Important:</b> If you see this test fail and the initial settings are still
  * correct, check the assumptions above (on fresh JVM fork).
  */
-public class KryoSerializerConcurrencyCheckInactiveITCase {
+public class KryoSerializerConcurrencyCheckInactiveITCase extends TestLogger {
 
 	// this sets the debug initialization back to its default, even if
 	// by default tests modify it (implicitly via assertion loading)
@@ -47,6 +50,9 @@ public class KryoSerializerConcurrencyCheckInactiveITCase {
 	 */
 	@Test
 	public void testWithNoConcurrencyCheck() throws Exception {
+		// this test will fail on DEBUG log level: If we run the test with DEBUG log level
+		// the KryoSerializer.CONCURRENT_ACCESS_CHECK will be enabled, causing a failure here.
+		assumeFalse(log.isDebugEnabled());
 		boolean assertionError;
 		try {
 			new KryoSerializerConcurrencyTest().testConcurrentUseOfSerializer();