-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
BlockingIOError: [Errno 11] write could not complete without blocking #3171
Comments
Never mind, happened in an older version too! |
Hi, @codingjoe ,I have same probably, Could you please tell how did you fix it .I run pytest only fail under jenkins .
|
@x007007007 I don't remember ¯_(ツ)_/¯ But reading my comment, I guess I just updated to the latest version of pytest. Sorry I can't be of more help. |
@codingjoe Sorry I don't have clear description my question, I'm run at newest pytest(3.4.2). and I try to switch different version all of them didn't work. I think this issue resolve my question travis-ci/travis-ci#4704. |
I've seen the same |
I have seen this happening sometimes with uwsgi in django. |
I am curious, is any uwsgi code actually executed in your test suite? That seems rather unlikely to me, in most uses cases people wouldn't spin up a WSGI server during a test run. |
What OS or CI provider are you using? |
@codingjoe For my stuff, uwsgi is used in our prod environment. We use django runsrever in our test environment. |
OS: Ubuntu Trusty (travis-ci; container; sudo=false)
Python: 3.6.4
xdist: n3
There isn't much I can explain, but that this happens to some, but not all our test groups. Happens only with the latest release.
Exception
requirements.txt
The text was updated successfully, but these errors were encountered: