-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
BlackDTestCase.test_cors_preflight failure on 22.8.0 #3251
Comments
Hmm, the OSError sounds like a host issue where some application or code is opening many files and isn't closing them. (Are there many other processes on the system?) I don't believe Black leaks file descriptors anywhere? Blackd could be leaking some, but I have no idea. |
It's a build server used for Arch Linux packages. The test passes and the build completes when done locally 👍. |
Ah thanks for checking! Is something on Black's end we can do to help with this, or can we close this issue as "check the downstream build server for FD overusage"? |
The discrepancy between local and remote could be due to the higher thread count on the build box (64 threads). The default open file limit is 1024 and running the test suite with so many threads somehow reaches it. If a fix cannot be implemented upstream, a downstream workaround would be to |
Alright thanks for the insights, I can try investigating later. It is surprising how a single pytest run would run into an open file limit of 1024. |
Indeed, which makes it more likely that open files from previous tests are involved. If I run only the 16 tests from |
Describe the bug
BlackDTestCase.test_cors_preflight test failure:
show/hide
To Reproduce
https://github.com/archlinux/svntogit-community/blob/8ef0305f6c9b28df533696a7e54d08269dc75aa8/trunk/PKGBUILD#L33-L35
The package build process also hangs after the above output.
Expected behavior
Test passes and we all live happily ever after.
Environment
Additional context
Can provide dependency versions if that would help.
The text was updated successfully, but these errors were encountered: