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
Issue Description - Option to Print failure to console
I'm currently doing performance test, and finding it hard to trace the failure from failure message received on client side. I'm using headless server, so there's no way to trace it like a web UI do.
Expected Behaviour
Logging failure to file whenever get non 200 response code
Actual behavior
I also checked the code, and find out that print_error_log only called when locust is shutting down, and it will print all the errors. Will be nice if we could get the failure logged to file.
The text was updated successfully, but these errors were encountered:
Issue Description - Option to Print failure to console
I'm currently doing performance test, and finding it hard to trace the failure from failure message received on client side. I'm using headless server, so there's no way to trace it like a web UI do.
Expected Behaviour
Logging failure to file whenever get non 200 response code
Actual behavior
I also checked the code, and find out that print_error_log only called when locust is shutting down, and it will print all the errors. Will be nice if we could get the failure logged to file.
The text was updated successfully, but these errors were encountered: