-
Notifications
You must be signed in to change notification settings - Fork 129
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
Test regressions introduced in #453 #459
Comments
I also encountered this on my Ubuntu 20.04 environment. I think it is caused due to difference in pip dependencies. My intuition is that at a newer versions pytest checks for resources that are not freed at the end of tests. |
Yep, that looks like the same kind of errors. Thanks for sharing your logs and package lists.
I think that's right. I first noticed the error after bumping my pytest version.
That's what I thought too, but I haven't been find the time to audit all of the uses of sockets in the codebase to narrow down the cause. As a result I've just been marking failing tests as Cheers, |
BTW I wasn't able to narrow down whether the unclosed resource is from a subprocess (#326), or an open logfile / other resource. |
One strategy to debug this is to log the stack and file descriptor when file descriptors are opened. Then you would know which file descriptor is left open. |
That's a good idea :) I'll try and carve out some time in mid January to take a look. Cheers, |
These should be addressed by the new Popen() usage. Issue facebookresearch#459.
🐛 Bug
This issue tracks progress towards addressing the errors of the type:
that were introduced in #453.
The text was updated successfully, but these errors were encountered: