-
Notifications
You must be signed in to change notification settings - Fork 3k
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
The locust chart shows that data is still being recorded after the timed run time expires #2910
Comments
Same issue. I commented out a line to fix this:
I think this is a way to update the results as you perform the loadtest, but the loadtest is over when you get the report, so you should not update. |
@andrewbaldwin44 and I are pretty busy at the moment. @PlanetartRoc 's fix looks promising (feel free to make a PR) and @zhenhuaplan second issue is also worth investigating. |
Prerequisites
Description
When I started locust, I set a scheduled operation task for 2.5 hours. After the completion of the task, the report shows that the task is executed in 2024/9/23 22:01:07 to 2024/9/24 00:31:07. However, when I check the report on the web interface at 2024/9/24 08:09:00, Found that the timeline of the chart goes straight to 2024/9/24 08:09:00
I use the following command

Command line
locust -f ./locust_run.py --master --master-bind-port=8682 --web-port=8677
Locustfile contents
Python version
3.9.9
Locust version
2.31.6
Operating system
Huawei Cloud EulerOS (Linux)
The text was updated successfully, but these errors were encountered: