Test process hanging forever about execnet HOT 8 CLOSED

Original comment by @mgoral

Hello,

exactly same issue here, but with pytest 2.9.0, xdist 1.14 and execnet 1.4.1. In my situation child process was previously killed/died because of something, which execnet additionally reported by printing to stderr: killing: [Errno 3] No such process

Adding any timeout to workerpool.waitall(), be it the one passed into safe_terminate or any hardcoded value seems to fix the problem.

from execnet.

Not sure if we could be hitting this issue as well (opensistemas-hub/osbrain#182).

from execnet.

this was fixed in aca6845

from execnet.

@RonnyPfannschmidt I'm still experiencing an issue where my code appears to get stuck in the reply.get() just above the waitall(timeout=timeout) that was added in aca6845

Would it be possible to just pass through the same timeout there, as well?

from execnet.

I believe so, but someone has to implement it

from execnet.

When you say that, do you just mean that someone has to create a PR with that change I suggested (reply.get(timeout=timeout)), or that an implementation has to be added somewhere else (I don't think this is the case, since Reply::get does already receive the timeout parameter and implements it)?

If you think there's nothing else to be done over and above that, I can create a tiny PR with that change

from execnet.

I hadn't have a chance to investigate, but it should be a step in the right direction

from execnet.

Ok, great, I created that as a PR just to move discussion over to there in case there is anything else to say about this

from execnet.