-
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
(libev) select: Invalid argument when trying to go past 1k users #121
Comments
What version of gevent are you running? Could try upgrading to the latest version? 1.0 was released just a month ago. |
gevent 1.0:
libev from macports is 4.15:
that's also the latest released (http://dist.schmorp.de/libev/) |
Sounds like it could be caused by the limit of 1024 file-descriptiors on I couldn't reproduce it when I tried it briefly on my MBA. I'll dig into it further. |
Could be a macports problem then, and a configuration issue with the On Sun, Jan 5, 2014 at 7:24 PM, Joakim Hamrén [email protected]:
|
Can anyone confirm if this is still an issue? I'm not able to reproduce with my MBP: libev 4.22 (installed with brew, not macports though) |
I confirm this on macOS High Sierra with libev 4.24 (bottled).
|
this is actually different than the original issue described. You are receiving a totally different stacktrace.
Have you increased file descriptors in your OS? If not, you need to. This may be considered a bug in gevent, requests, or urllib3 for not handling the situation gracefully when you run out of file descriptors... but I don't see an actual Locust issue we can take action on besides aborting a test once you exhaust file descriptors. I am closing this issue for now since there is nothing actionable to fix for Locust. |
MacOS X 10.9, python 2.7 (macports)
Latest locust (github), latest pip packages
Testing a local setup, trying to break past 1000 users. I'm able to load up to 1000 users just fine (after bumping my ulimit), but locust crashes out past that point:
https://gist.github.com/TTimo/8149351
The text was updated successfully, but these errors were encountered: