showuon commented on PR #14506: URL: https://github.com/apache/kafka/pull/14506#issuecomment-1805023823
I had a look, and think this flaky test should be the infra's issue, not our code. Like you said, in 3.6 branch, after I backported this PR, it started to fail (on Nov. 9). Now, checking trunk build, it also failed on Nov. 9 and 10. https://ge.apache.org/scans/tests?search.names=git%20branch&search.rootProjectNames=kafka&search.startTimeMax=1699587001012&search.startTimeMin=1696089600000&search.timeZoneId=Asia%2FTaipei&search.values=trunk&tests.container=org.apache.kafka.clients.ClusterConnectionStatesTest# Back to the test code, it failed at this line: `assertEquals(1, ClientUtils.resolve("localhost", singleIPHostResolver).size());` which basically our kafka logic won't impact this host resolver results. So, I think we can keep monitoring it for now, and hope it can be self-healing. If not, we raise a issue to infra team, maybe? -- 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]
