showuon opened a new pull request #9775: URL: https://github.com/apache/kafka/pull/9775
Looking into this flaky test, the error messages are: ``` Timed out before consuming expected 1350 records. The number consumed was 1230. ``` https://ci-builds.apache.org/job/Kafka/job/kafka-trunk-jdk8/303/testReport/kafka.api/PlaintextConsumerTest/testLowMaxFetchSizeForRequestAndPartition/ ``` Timed out before consuming expected 1350 records. The number consumed was 1200. ``` https://ci-builds.apache.org/job/Kafka/job/kafka-trunk-jdk8/305/testReport/kafka.api/PlaintextConsumerTest/testLowMaxFetchSizeForRequestAndPartition/ ``` Timed out before consuming expected 1350 records. The number consumed was 1215. ``` https://ci-builds.apache.org/job/Kafka/job/kafka-trunk-jdk8/305/testReport/junit/kafka.api/PlaintextConsumerTest/testLowMaxFetchSizeForRequestAndPartition/ And after checking the test, I found the test is expected to be slow because it tests `we can consume all partitions if fetch max bytes and max.partition.fetch.bytes are low`. So the test has no bug, just need more time. What I did are: 1. reduce the record size for each partition (from 15 -> 10), it should speed up the test, but also be able to test the original scenario 2. increase the timeout value (from 60 sec -> 90 sec) Hope this can makes the test more reliable! ### Committer Checklist (excluded from commit message) - [ ] Verify design and implementation - [ ] Verify test coverage and CI build status - [ ] Verify documentation (including upgrade notes) ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
