You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Divij Vaidya (Jira)" <ji...@apache.org> on 2022/05/31 13:46:00 UTC

[jira] [Commented] (KAFKA-13951) Fix flaky test KRaftClusterTest.testCreateClusterAndCreateListDeleteTopic

    [ https://issues.apache.org/jira/browse/KAFKA-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544399#comment-17544399 ] 

Divij Vaidya commented on KAFKA-13951:
--------------------------------------

The stack trace shows that the topic already existed. It can only exist if the directories weren't cleaned up properly at the end of one of the previous tests and hence, when a new cluster was started it assumed that topic already exists.

> Fix flaky test KRaftClusterTest.testCreateClusterAndCreateListDeleteTopic
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-13951
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13951
>             Project: Kafka
>          Issue Type: Test
>            Reporter: Divij Vaidya
>            Priority: Major
>
> Example of failure at [https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka-pr/detail/PR-12229/1/tests]
> Stack trace:
> {noformat}
> Stacktrace
> java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.TopicExistsException: Topic 'test-topic' already exists.
> 	at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
> 	at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1908)
> 	at org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:165)
> 	at kafka.server.KRaftClusterTest.testCreateClusterAndCreateListDeleteTopic(KRaftClusterTest.scala:115)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:498)
> 	at org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:725)
> 	at org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
> 	at org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
> 	at org.junit.jupiter.engine.extension.TimeoutInvocation.proceed(TimeoutInvocation.java:46)
> 	at org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:149)
> 	at org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:140)
> 	at org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:84)
> 	at org.junit.jupiter.engine.execution.ExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(ExecutableInvoker.java:115)
> 	at org.junit.jupiter.engine.execution.ExecutableInvoker.lambda$invoke$0(ExecutableInvoker.java:105)
> 	at org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106){noformat}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)