10000 HTML report: %KO - NaN vs 0.00 · Issue #4611 · gatling/gatling · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

HTML report: %KO - NaN vs 0.00 #4611

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
rado-o opened this issue Feb 20, 2025 · 5 comments
Closed

HTML report: %KO - NaN vs 0.00 #4611

rado-o opened this issue Feb 20, 2025 · 5 comments
Assignees
Milestone

Comments

@rado-o
Copy link
rado-o commented Feb 20, 2025

I bumped Gatling Java dependency to version 3.13.4 (previously used version: 3.12.0).
All executed requests were successful. However, the KO percentage is not consistent in the HTML report: for the most requests a double value (0.00) is logged for %KO. For some requests "NaN" is logged. Please see the attached screenshot for the reference.
My assumption: In the previous version there is no comma present for a higher count of requests, example: 49224. In the current version there is a comma present, example 49,224. I think the value cannot be parsed properly when counting percentage.

Current version 3.13.4:
Image

Version 3.12.0:
Image

Gatling version: 3.13.4
Java version: 21.0.5
Kotlin version: 2.1.10

@slandelle
Copy link
Member

Please share your log file.

@rado-o
Copy link
Author
rado-o commented Feb 20, 2025

Hi @slandelle ,

I created a dummy repository and reproduced the issue: please see the log file along with HTML report.

computerdatabasesimulation-20250220131633817.zip

@slandelle slandelle self-assigned this Feb 20, 2025
@slandelle slandelle added this to the 3.13.5 milestone Feb 20, 2025
@slandelle
Copy link
Member

Thanks! Will release a fix next week.

@slandelle
Copy link
Member

Gatling 3.13.5 is out

@usteinkopf
Copy link

Hi, anybody know, since when this bug occurs? We can't go to 3.13.5 because 3.13.5 dumped Jenkinssupport.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants
0