Skip to content

Fix computation of min in Summary report#6044

Merged
vlsi merged 1 commit into
apache:masterfrom
vlsi:calculator
Jul 12, 2023
Merged

Fix computation of min in Summary report#6044
vlsi merged 1 commit into
apache:masterfrom
vlsi:calculator

Conversation

@vlsi

@vlsi vlsi commented Jul 12, 2023

Copy link
Copy Markdown
Collaborator

Fixes #6043

@vlsi vlsi added this to the 5.6.3 milestone Jul 12, 2023
@vlsi
vlsi merged commit ce1f32a into apache:master Jul 12, 2023
@ashokelu

Copy link
Copy Markdown

This issue is still there in 5.6.3

@jenero77

jenero77 commented Dec 1, 2025

Copy link
Copy Markdown

Yes, one and a half year later the bug is still there.
I think the reason is that there is a "Thread finished" entry with elapsed time = 0 in the result file. This leads to this min time as far as I can see. Fix it, please, it messes up the reports...

@nakkeeran2505

Copy link
Copy Markdown

This issue has been there at least from 2020 - Link . Kindly please look into this. If I am not wrong, this issue does not exist in JMeter 5.1.1 version. Please check it as reference.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Jmeter 5.6 shows 0 as a min response time in summary report

4 participants