chia7712 commented on PR #15904:
URL: https://github.com/apache/kafka/pull/15904#issuecomment-2104903142

   > Have the 30 test failures been triaged?
   
   |test|jira|
   |  ----  | ----  |
   |testSyncTopicConfigs|https://issues.apache.org/jira/browse/KAFKA-15945|
   
|testReplicateSourceDefault|https://issues.apache.org/jira/browse/KAFKA-15292|
   
|testProduceConsumeWithWildcardAcls|https://issues.apache.org/jira/browse/KAFKA-16697|
   |testFenceMultipleBrokers|https://issues.apache.org/jira/browse/KAFKA-16634|
   |testSeparateOffsetsTopic|https://issues.apache.org/jira/browse/KAFKA-14089|
   
|testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl|https://issues.apache.org/jira/browse/KAFKA-8250|
   
|testDescribeQuorumReplicationSuccessful|https://issues.apache.org/jira/browse/KAFKA-15104|
   
|testDescribeQuorumStatusSuccessful|https://issues.apache.org/jira/browse/KAFKA-16174|
   
|testTaskRequestWithOldStartMsGetsUpdated|https://issues.apache.org/jira/browse/KAFKA-16136|
   
|testConsumptionWithBrokerFailures|https://issues.apache.org/jira/browse/KAFKA-15146|
   |testCoordinatorFailover|https://issues.apache.org/jira/browse/KAFKA-16024|
   
|testBrokerHeartbeatDuringMigration|https://issues.apache.org/jira/browse/KAFKA-15963|
   
|testAbortTransactionTimeout|https://issues.apache.org/jira/browse/KAFKA-15772|
   
|testMultiConsumerStickyAssignor|https://issues.apache.org/jira/browse/KAFKA-15934|
   
|testDynamicIpConnectionRateQuota|https://issues.apache.org/jira/browse/KAFKA-16698|
   
|testCreateClusterAndPerformReassignment|https://issues.apache.org/jira/browse/KAFKA-15103|
   
|shouldBootstrapTwoBrokersWithFollowerThrottle|https://issues.apache.org/jira/browse/KAFKA-4184|
   
   Besides, the thread leaks should be fixed by #15886. Hence, I will rebase 
code to trigger QA again.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to