-
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
test_stop is fired twice when Locust is running in –master/worker mode #1638
Comments
This behaviour relates to quitting test_stop.fire being called both here: https://github.com/locustio/locust/blob/master/locust/runners.py#L575 and here: https://github.com/locustio/locust/blob/master/locust/runners.py#L581 I'm not sure what the best way to fix this is. @heyman You originally wrote the code, maybe you have an opinion? |
This sounds like a bug to me. I'll see if I can produce a test (and a fix) for it. |
PR here: #1641 The whole machinery keeping track of Runners and their states could probably use some rework at some point. The current code has evolved over time with patch upon patch and feels a bit brittle at the moment. |
Should be fixed now. If you can't wait for it to make it into a release, you can run from latest master: pip3 install -e git://github.com/locustio/locust.git@master#egg=locust |
I did a quick retest with two workers on |
when I run locust in –master/worker mode,test_stop is fired twice, but test_start is fired once.
my user class:
the test command:
the log information:
The text was updated successfully, but these errors were encountered: