-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
TestStdCaptureFD tests failing with "4 FD leackage detected" (sic; s/leackage/leakage/) #492
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
Comments
Original comment by Marc Abramowitz (BitBucket: msabramo, GitHub: msabramo): Pull request to fix the "leackage" typo: https://bitbucket.org/hpk42/pytest/pull-request/135/fix-typo-fd-leackage-fd-leakage/diff |
Original comment by Marc Abramowitz (BitBucket: msabramo, GitHub: msabramo): Random idea: Pull out of pytest the logic for detecting file descriptor leaks and make it into a py.test plugin so that it can be used by other projects. Sort of like drippy (https://launchpad.net/drippy) for nose. |
Original comment by Marc Abramowitz (BitBucket: msabramo, GitHub: msabramo): Here's something interesting. If running only a subset of the tests, this problem may or may not show up. Here's how things look.
Interesting that it only happens if those two tests are run together.
|
Original comment by Marc Abramowitz (BitBucket: msabramo, GitHub: msabramo): Pull request #137 changes the fd leak detection to use psutil instead of
Note how this points out clearly that the issue here is:
|
Originally reported by: Marc Abramowitz (BitBucket: msabramo, GitHub: msabramo)
I am periodically seeing failures due to file descriptor leakage in both builds on Drone.io (e.g.: https://drone.io/bitbucket.org/msabramo/pytest/6) and locally using
tox
:From https://drone.io/bitbucket.org/msabramo/pytest/6:
From a local
tox
run:The text was updated successfully, but these errors were encountered: