[ https://issues.apache.org/jira/browse/KAFKA-14014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573211#comment-17573211 ]
Matthew de Detrich edited comment on KAFKA-14014 at 7/30/22 5:57 AM: --------------------------------------------------------------------- In case people want to reproduce the flakiness, assuming you have a working docker installation you can do the following {code:java} docker run -it --cpus=2 --rm -u gradle -v "$PWD":/home/gradle/project -w /home/gradle/project gradle sh{code} where cpus=2 is how you can toggle how many cpus you want (there is a tradeoff between higher occurrence to encounter the flakiness vs how fast the test runs). I wouldn't recommend doing lower than cpus=2 otherwise even building the kafak project in gradle can take ages. The above command will put you into a shell at which point you can do {code:java} while [ $? -eq 0 ]; do ./gradlew :streams:test --tests org.apache.kafka.streams.integration.NamedTopologyIntegrationTest.shouldAllowRemovingAndAddingNamedTopologyToRunningApplicationWithMultipleNodesAndResetsOffsets; done{code} Which will re-run the tests until there is a failure. Note that due to how Gradle cache's test runs, you need to do something like [https://github.com/gradle/gradle/issues/9151#issue-434212465] in order to force gradle to re-run the test every time. was (Author: mdedetrich-aiven): In case people want to reproduce the flakiness, assuming you have a working docker installation you can do the following {code:java} docker run -it --cpus=2 --rm -u gradle -v "$PWD":/home/gradle/project -w /home/gradle/project gradle sh{code} where cpus=2 is how you can toggle how many cpus you want (there is a tradeoff between higher occurrence to encounter the flakiness vs how fast the test runs). I wouldn't recommend doing lower than cpus=2 otherwise even building the kafak project in gradle can take ages. The above command will put you into a shell at which point you can do {code:java} while [ $? -eq 0 ]; do ./gradlew :streams:test --tests org.apache.kafka.streams.integration.NamedTopologyIntegrationTest.shouldAllowRemovingAndAddingNamedTopologyToRunningApplicationWithMultipleNodesAndResetsOffsets; done{code} Which will re-run the tests until there is a failure. > Flaky test > NamedTopologyIntegrationTest.shouldAllowRemovingAndAddingNamedTopologyToRunningApplicationWithMultipleNodesAndResetsOffsets() > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: KAFKA-14014 > URL: https://issues.apache.org/jira/browse/KAFKA-14014 > Project: Kafka > Issue Type: Test > Components: streams > Reporter: Bruno Cadonna > Priority: Critical > Labels: flaky-test > > {code:java} > java.lang.AssertionError: > Expected: <[KeyValue(B, 1), KeyValue(A, 2), KeyValue(C, 2)]> > but: was <[KeyValue(B, 1), KeyValue(A, 2), KeyValue(C, 1)]> > at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) > at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:6) > at > org.apache.kafka.streams.integration.NamedTopologyIntegrationTest.shouldAllowRemovingAndAddingNamedTopologyToRunningApplicationWithMultipleNodesAndResetsOffsets(NamedTopologyIntegrationTest.java:540) > at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) > at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:568) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at > org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:299) > at > org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:293) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at java.base/java.lang.Thread.run(Thread.java:833) > {code} > https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-12310/2/testReport/junit/org.apache.kafka.streams.integration/NamedTopologyIntegrationTest/Build___JDK_11_and_Scala_2_13___shouldAllowRemovingAndAddingNamedTopologyToRunningApplicationWithMultipleNodesAndResetsOffsets/ > https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-12310/2/testReport/junit/org.apache.kafka.streams.integration/NamedTopologyIntegrationTest/Build___JDK_17_and_Scala_2_13___shouldAllowRemovingAndAddingNamedTopologyToRunningApplicationWithMultipleNodesAndResetsOffsets/ -- This message was sent by Atlassian Jira (v8.20.10#820010)