divijvaidya opened a new pull request, #14273:
URL: https://github.com/apache/kafka/pull/14273
## Exception stack trace
```
org.opentest4j.AssertionFailedError: expected: <3> but was: <1>
at
app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at
app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at
app//org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
at
app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
at
app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
at
app//org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:528)
at
app//kafka.api.PlaintextAdminIntegrationTest.testCreatePartitions(PlaintextAdminIntegrationTest.scala:705)
```
## Examples of CI build failures
https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-14135/10/testReport/junit/kafka.api/PlaintextAdminIntegrationTest/Build___JDK_11_and_Scala_2_13___testCreatePartitions_String__quorum_zk/
## Reason for failure
We don't wait for metadata propagation before asserting for changes made in
previous step.
## Fix
1. Use existing `TestUtils.waitForAllPartitionsMetadata`
2. We cannot use `TestUtils.waitForAllPartitionsMetadata` at all places
since the test wants to print additional information. In such cases use the
existing method with correct parameters in test which was added in
https://github.com/apache/kafka/commit/a5d21faf4e2d308828153be2576026f5dfe11f32
to de-flake the test.
--
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: jira-unsubscr...@kafka.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
