Negative min_response_time shown in stats
See original GitHub issueDescribe the bug
Negative value shown for min_response_time
:
Expected behavior
0 or positive value.
Actual behavior
Negative value shown for min_response_time
Steps to reproduce
I have a branch local docker-compose setup to reproduce it easily. But it’s just 1 worker calling nginx in another docker container.
Environment
- OS: Docker
- Python version: -
- Locust version: current master
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Interpreting "Response time is negative, can not update ...
The error simply implies that the response time for the current request came out to be negative (possibly due to momentary failure of...
Read more >Response Time Calculation between 2 different events
Hello, I am trying to find response time between events in different sourcetype but not able to figure out how to find time...
Read more >How to remove HTTPError 429 from Locust API Statistics?
When 429 errors start occurring the min response time is less than 10ms. This leads to the statistics being skewed by the response...
Read more >HTTP: response time measurement omits time to connect and ...
@ceeaspb : Ah, my bad, after checking a bit further, the culprit is ResponseBuilder, how it is updated. Gatling doesn't update those timestamps ......
Read more >Gatling simulation assertions failed ! - Google Groups
i have problem with gatling, i know scala/maven since yesterday. the error is : Failed to execute goal io.gatling:gatling-maven-plugin:2.1.2 ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Interesting.
I don’t think we should “hide” the clock issue by setting it to zero if it’s negative.
Done: https://github.com/locustio/locust/pull/1492