apoorvmittal10 commented on PR #14620: URL: https://github.com/apache/kafka/pull/14620#issuecomment-1826401674
@AndrewJSchofield @philipnee Thanks for approving the PR. @xvrl I have also added support for handling temporality change in KafkaMetricsCollector ([KAFKA-15877](https://issues.apache.org/jira/browse/KAFKA-15877)). Below is the status of build which reports 11 failing tests where none of the test is related to the changes in the PR. However I investigated and can find, among 11, 10 already have jira reported as per other PR build failure. I tried reproducing the 1 remaining tests and cannot reproduce hence have created jira to track same. @mjsax Please let me know if we can go ahead with the PR merge or I shall address something else as well? New failing - 11 `Already existing jira, flaky test already known`: Build / JDK 11 and Scala 2.13 / testResetSinkConnectorOffsetsOverriddenConsumerGroupId – org.apache.kafka.connect.integration.OffsetsApiIntegrationTest 16s: https://issues.apache.org/jira/browse/KAFKA-15891 `Already existing jira, flaky test already known`: Build / JDK 11 and Scala 2.13 / testResetSinkConnectorOffsetsZombieSinkTasks – org.apache.kafka.connect.integration.OffsetsApiIntegrationTest 59s: https://issues.apache.org/jira/browse/KAFKA-15524 `Already existing jira, flaky test already known`: Build / JDK 11 and Scala 2.13 / testResetSinkConnectorOffsetsZombieSinkTasks – org.apache.kafka.connect.integration.OffsetsApiIntegrationTest 52s: https://issues.apache.org/jira/browse/KAFKA-15524 `Already existing jira, flaky test already known`: Build / JDK 11 and Scala 2.13 / testTaskRequestWithOldStartMsGetsUpdated() – org.apache.kafka.trogdor.coordinator.CoordinatorTest 2m 0s: https://issues.apache.org/jira/browse/KAFKA-15760 `Already existing jira, flaky test already known`: Build / JDK 17 and Scala 2.13 / testReplicateSourceDefault() – org.apache.kafka.connect.mirror.integration.IdentityReplicationIntegrationTest 1m 50s: https://issues.apache.org/jira/browse/KAFKA-15292 `Created jira, unable to reproduce locally`: Build / JDK 21 and Scala 2.13 / testOutdatedCoordinatorAssignment() – org.apache.kafka.clients.consumer.internals.EagerConsumerCoordinatorTest <1s: https://issues.apache.org/jira/browse/KAFKA-15900 `Already existing jira, flaky test already known`: Build / JDK 21 and Scala 2.13 / testFenceMultipleBrokers() – org.apache.kafka.controller.QuorumControllerTest 47s: https://issues.apache.org/jira/browse/KAFKA-15898 `Already existing jira, flaky test already known`: Build / JDK 21 and Scala 2.13 / testTaskRequestWithOldStartMsGetsUpdated() – org.apache.kafka.trogdor.coordinator.CoordinatorTest 2m 0s: https://issues.apache.org/jira/browse/KAFKA-15760 `Already existing jira, flaky test already known`: Build / JDK 8 and Scala 2.12 / shouldUpgradeFromEosAlphaToEosV2[true] – org.apache.kafka.streams.integration.EosV2UpgradeIntegrationTest 4m 23s: https://issues.apache.org/jira/browse/KAFKA-15797 `Already existing jira, flaky test already known`: Build / JDK 8 and Scala 2.12 / [1] Type=Raft-Combined, Name=testDescribeQuorumReplicationSuccessful, MetadataVersion=3.7-IV1, Security=PLAINTEXT – org.apache.kafka.tools.MetadataQuorumCommandTest 1m 7s: https://issues.apache.org/jira/browse/KAFKA-15104 `Already existing jira, flaky test already known`: Build / JDK 8 and Scala 2.12 / [5] Type=Raft-Combined, Name=testDescribeQuorumStatusSuccessful, MetadataVersion=3.7-IV1, Security=PLAINTEXT – org.apache.kafka.tools.MetadataQuorumCommandTest: https://issues.apache.org/jira/browse/KAFKA-15104 -- 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]
