Skip to content

Fix computation of min in Summary report #6044

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.

Sign up for GitHub

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

Jump to bottom
Merged
vlsi merged 1 commit into from
Jul 12, 2023
Merged

Fix computation of min in Summary report #6044

vlsi merged 1 commit into from
Jul 12, 2023

Conversation

@vlsi
Copy link
Collaborator

@vlsi vlsi commented Jul 12, 2023

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

ashokelu commented Jun 13, 2024

This issue is still there in 5.6.3

@jenero77
Copy link

jenero77 commented Dec 1, 2025

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...

@jenero77 jenero77 mentioned this pull request Dec 1, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

5.6.3

Development

Successfully merging this pull request may close these issues.

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

3 participants

@vlsi @ashokelu @jenero77