Skip to content
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

It'd be nice to include the machine that a logging message came from #67

Closed
sanga opened this issue Apr 19, 2013 · 1 comment
Closed

Comments

@sanga
Copy link
Contributor

sanga commented Apr 19, 2013

In a large environment with many slaves, if one slave happens to be misconfigured (incorrect dependencies or something) it's currently difficult to see where an error has come from. I didn't see any standard way of doing this in python logging module so hatched the following (hackish) solution:

sanga@225d48c

Is there a proper way to do this? Or would something like the above be OK?

@sanga
Copy link
Contributor Author

sanga commented Sep 5, 2013

a cleaner solution: #89

@sanga sanga closed this as completed Sep 5, 2013
pancaprima pushed a commit to pancaprima/locust that referenced this issue May 28, 2018
* redirect to base url for new test

* Update web.py
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant