[KAFKA-14534] Flaky Test TransactionsExpirationTest.testTransactionAfterProducerIdExpires

• Type: Test
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.5.0
• Labels: flaky-test
• Assignee: Greg Harris
• Reporter: Greg Harris
• Created: 19/Dec/22 22:51
• Updated: 06/Jan/23 19:26
• Resolved: 23/Dec/22 09:33

Description

This test has failed in several recent builds:
    https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka/detail/trunk/1447/tests/
        org.opentest4j.AssertionFailedError: expected: <0> but was: <1>
    https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka/detail/trunk/1443/tests/
        org.opentest4j.AssertionFailedError: expected: <0> but was: <1>
    https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka/detail/trunk/1440/tests/
        org.opentest4j.AssertionFailedError: expected: <0> but was: <1>
    https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka/detail/trunk/1439/tests/
        org.opentest4j.AssertionFailedError: expected: <0> but was: <1>
    https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka/detail/trunk/1439/tests/
        org.opentest4j.AssertionFailedError: expected: <0> but was: <1>
    https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka/detail/trunk/1436/tests/
        org.opentest4j.AssertionFailedError: expected: <0> but was: <1>

The stacktrace is as follows:

org.opentest4j.AssertionFailedError: expected: <0> but was: <1>
	at app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
	at app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
	at app//org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
	at app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:166)
	at app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:161)
	at app//org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:628)
	at app//kafka.api.TransactionsExpirationTest.testTransactionAfterProducerIdExpires(TransactionsExpirationTest.scala:158)
	at java.base@11.0.16.1/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base@11.0.16.1/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base@11.0.16.1/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base@11.0.16.1/java.lang.reflect.Method.invoke(Method.java:566)
...

 

This corresponds to the producer ID assertion in the test, and seems to indicate that the test sometimes does not re-use the producer id.

Issue Links

• is related to: KAFKA-14600 Flaky test ProducerIdExpirationTest
• relates to: KAFKA-14097 Separate configuration for producer ID expiry
• links to: GitHub Pull Request #13036