Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
1.1.1, 2.2.0, 2.3.0
Description
To get stable nightly builds for `2.2` release, I create tickets for all observed test failures.
https://jenkins.confluent.io/job/apache-kafka-test/job/2.2/21/
java.lang.AssertionError: Received 0, expected at least 68 at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.assertTrue(Assert.java:41) at kafka.api.ConsumerBounceTest.receiveAndCommit(ConsumerBounceTest.scala:557) at kafka.api.ConsumerBounceTest.$anonfun$testRollingBrokerRestartsWithSmallerMaxGroupSizeConfigDisruptsBigGroup$1(ConsumerBounceTest.scala:320) at kafka.api.ConsumerBounceTest.$anonfun$testRollingBrokerRestartsWithSmallerMaxGroupSizeConfigDisruptsBigGroup$1$adapted(ConsumerBounceTest.scala:319) at scala.collection.mutable.ResizableArray.foreach(ResizableArray.scala:62) at scala.collection.mutable.ResizableArray.foreach$(ResizableArray.scala:55) at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:49) at kafka.api.ConsumerBounceTest.testRollingBrokerRestartsWithSmallerMaxGroupSizeConfigDisruptsBigGroup(ConsumerBounceTest.scala:319)
Attachments
Issue Links
- contains
-
KAFKA-7936 Flaky Test ConsumerBounceTest#testRollingBrokerRestartsWithSmallerMaxGroupSizeConfigDisruptsBigGroup
- Resolved
- is duplicated by
-
KAFKA-8260 Flaky test ConsumerBounceTest#testRollingBrokerRestartsWithSmallerMaxGroupSizeConfigDisruptsBigGroup
- Resolved
- is fixed by
-
KAFKA-9844 Maximum number of members within a group is not always enforced due to a race condition in join group
- Resolved
- is related to
-
KAFKA-7540 Flaky Test ConsumerBounceTest#testClose
- Resolved
- relates to
-
KAFKA-7964 Flaky Test ConsumerBounceTest#testConsumerReceivesFatalExceptionWhenGroupPassesMaxSize
- Open
-
KAFKA-9885 Evict last members of a group when the maximum allowed is reached
- Resolved
- links to