-
Notifications
You must be signed in to change notification settings - Fork 538
pytest: bad address #460
Comments
While I do not understand yet why Errno 14 is thrown, this error usually indicated a problem with the notebooks. It happened some times before too.. |
Happened again in http://ci.mxnet.io/blue/organizations/jenkins/gluon-nlp/detail/PR-500/3/pipeline/ |
Seems to be the same problem. http://ci.mxnet.io/blue/organizations/jenkins/gluon-nlp/detail/PR-509/1/pipeline/23 |
I searched this problem and not much came up. There are claims that this was a bug in py2.6 but we have occurrences in both py27 and py36 Searching for |
Done. Let's see if this addresses the problem. |
So far it hasn't been occured yet. I will leave the issue open for another couple of days. |
Closing as I haven't seen this occurring again. |
Unfortunately it occurred again. http://ci.mxnet.io/blue/organizations/jenkins/gluon-nlp/detail/PR-617/1/pipeline/23#step-54-log-738 |
Since pytest-xdist uses multi-process as a way to speed up tests, bad address here indicates that a worker process has died, which usually indicates actual problems in code. I found this out because there was a recent regression that causes some scripts to run into exception which kills a testing worker process. |
Tracked at apache/mxnet#13875 |
Sometimes CI is not very stable:
http://ci.mxnet.io/blue/organizations/jenkins/gluon-nlp/detail/PR-387/15/
The text was updated successfully, but these errors were encountered: