You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user starts a load test and the test_start event is fired, the UI is basically doing nothing until the test_start event hooks have finished executing.
Expected behavior
UI should open up the statistics dashboard and change the status from READY to a new state called INITIALIZING.
Actual behavior
UI hangs on "Start new Locust run screen" until test_start execution has finished.
Steps to reproduce
Add a test_start listener that pauses the thread for 5 seconds.
I looked into this and I found that there is a relatively easy way to fix it (without changing too much the current ways). I put a PR for this (#1479). However, the displayed state is not 'fully' consistent (it says ready while in reality is preparing).
A better (but more involved) solution would be to add an extra state signaling that the test_start events are running (something like PREPARING).
Describe the bug
When a user starts a load test and the
test_start
event is fired, the UI is basically doing nothing until thetest_start
event hooks have finished executing.Expected behavior
UI should open up the statistics dashboard and change the status from
READY
to a new state calledINITIALIZING
.Actual behavior
UI hangs on "Start new Locust run screen" until
test_start
execution has finished.Steps to reproduce
test_start
listener that pauses the thread for 5 seconds.Environment
locust
The text was updated successfully, but these errors were encountered: