[
https://issues.apache.org/jira/browse/KAFKA-19672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18018673#comment-18018673
]
ally heev commented on KAFKA-19672:
-----------------------------------
It might be possible that printWindow is called after printTotal in some runs
as it is asynchronously
[called|https://github.com/apache/kafka/blob/c565ba1a04f30452500dbf1075f74866deb535ca/tools/src/main/java/org/apache/kafka/tools/ProducerPerformance.java#L558]
Relying on last line is quite error-prone anyway. I have seen this practice in
many tests
> Producer performance test failing in parsing aggregate statistics
> -----------------------------------------------------------------
>
> Key: KAFKA-19672
> URL: https://issues.apache.org/jira/browse/KAFKA-19672
> Project: Kafka
> Issue Type: Bug
> Components: system tests
> Reporter: ally heev
> Priority: Major
> Attachments: benchmark_test.log
>
>
> When running benchmark test, some of the producer perf tests are failing in
> statistics parsing. Logs attached
> cmd: `TC_PATHS="tests/kafkatest/benchmarks/core/benchmark_test.py" bash
> tests/docker/run_tests.sh`
> JDK: `azul/zulu-openjdk:17`(used azul's jdk because with openjdk tests were
> failing to run)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
