Closed harkiranjeetkaur closed 2 years ago
I'm seeing this issue as well. I think this is because the occurrences are aggregated in Locust, and the occurrences counter is never reset. See:
I think the solution is to reset the occurrences counter to 0 before/after a message is sent to the master node.
Hi,
The occurrences of the failure is giving an irrelevant number in the results. The way we are grabbing this variable is as following in the Locust master python class:
Task class
We are appending a unique random id to each execute() block, so that no two runs are similar.
Locust util record failure method
And also that unique id is appended to the failure record. Ideally no two failures should have similar method or name. How is occurrence variable getting its value then?