-
Notifications
You must be signed in to change notification settings - Fork 68
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
[Bug] Too many open files (on OSX aarch64) when setting up test environment #1475
Comments
cc @snapbug |
If you set ulimit to something like 1024, this goes away. It'd be nice for rattler to query the limits and then not blow through them. |
@beckermr unfortunately ulimit doesn't persist due to OSX's system integrity protection. So you either have to set it immediately before invoking rattler-build or something like That does work as a workaround. |
We have a way of limiting the concurrency when linking files and we should use it. I think the installer struct has a flag for it. |
Yeah there should be a |
Starting with rattler-build 0.22.0 we can no longer build packages containing a test environment on OSX (at least on apple silicon). We experience failures with linking packages due to too many open files. I binary searched all the released versions from 0.21.0 (which works fine) to 0.38.0. Looks like the breakage occurred in 0.22.0.
Note that this issue does not occur on linux (tested on Linux x86_64 and Linux aarch64 w/ rattler-build 0.38.0).
My guess is maybe some kind of concurrency limit might be needed on OSX that respects the current ulimit.
The text was updated successfully, but these errors were encountered: