Skip to content
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

Modern UI: Wrong chart's legend for overridden percentiles values #2463

Closed
2 tasks done
zifter opened this issue Nov 14, 2023 · 3 comments · Fixed by #2464
Closed
2 tasks done

Modern UI: Wrong chart's legend for overridden percentiles values #2463

zifter opened this issue Nov 14, 2023 · 3 comments · Fixed by #2464
Labels

Comments

@zifter
Copy link

zifter commented Nov 14, 2023

Prerequisites

Description

Step to reproduce:

  1. Change default percentiles

locust.stats.PERCENTILES_TO_CHART = [0.95, 0.99]

  1. Run any test

Expected

In chart's legend I see percentile 95, 99.
response_times_(ms)_1699955769

Result

In chart's legend I see percentile Median Response Time and 95% percentile
response_times_(ms)_1699955583 645

Command line

Locustfile contents

import locust.stats

locust.stats.PERCENTILES_TO_REPORT = [0.95, 0.99]
locust.stats.PERCENTILES_TO_CHART = [0.95, 0.99]

Python version

3.11

Locust version

2.18.3

Operating system

does not matter

@zifter zifter added the bug label Nov 14, 2023
@cyberw
Copy link
Collaborator

cyberw commented Nov 14, 2023

@andrewbaldwin44 this one is for you (but no rush :)

while you are at it, I think I saw quotation marks around ”number of users” in the bottom graph, which is kinda weird…

@cyberw
Copy link
Collaborator

cyberw commented Nov 14, 2023

(side note: it is weird that we are graphing median instead of average/mean)

@cyberw
Copy link
Collaborator

cyberw commented Nov 14, 2023

@zifter you can try out the fix using pip install -U --pre locust (in a few minutes)

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

Successfully merging a pull request may close this issue.

2 participants