Ken Huang

> @m1a2st can you pull in the latest trunk changes? I have added code to report the JUnit failures in the Github Actions workflows. I want to do a few...

I will check these tests which timeout 30 second - `ResetConsumerGroupOffsetTest.testResetOffsetsToEarliestOnTopicsAndPartitions` - `ResetConsumerGroupOffsetTest.testResetOffsetsAllTopicsAllGroups` - `DescribeConsumerGroupTest.testDescribeWithMultiPartitionTopicAndMultipleConsumers` - `DescribeConsumerGroupTest.testDescribeWithConsumersWithoutAssignedPartitions` - `ZkMigrationIntegrationTest.testMigrateTopicDeletions` - `ClientTelemetryTest.testClientInstanceId` --- This test is timeout for 120s - `KafkaAdminClientTest.testClientSideTimeoutAfterFailureToReceiveResponse`...

I open these jira tasks to trace these timeout tests https://issues.apache.org/jira/browse/KAFKA-17471 https://issues.apache.org/jira/browse/KAFKA-17472 https://issues.apache.org/jira/browse/KAFKA-17473

Hello @chia7712, The fail tests are: - `OffsetsApiIntegrationTest#testAlterSinkConnectorOffsetsDifferentKafkaClusterTargeted` the reason is can't met condition in 30s - `PlaintextConsumerSubscriptionTest` the reason is Failed to close kafka consumer I think we could...

@mumrah, Thanks for your reminder, we only add timeout for cluster tests in this PR, I should modify the title.

I consider the "@TestTemplate" is a symbol for these annotations `ClusterTest`, `ClusterTemplate`, `ClusterTests`, but I will fix the title more clearly.

Please resolve the conflict, thanks

@chia7712, Thanks for your comment, PTAL

Gentle ping, @chia7712, I update the title

@chia7712, Thanks for your comments, I will take a look at another types.