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
BUNDLE_GLOBAL_GEM_CACHE breaks natively compiled libraries #6616
Comments
I think this issue could be better summarized, "Some native extensions not reinstalled properly with BUNDLE_GLOBAL_GEM_CACHE=1". Here's how I reproduced the problem:
If I look at the
However, with the feature flag, I don't see, "Building native extensions. This could take a while...":
Is the idea the
Whereas for
|
Describe the problem as clearly as you can
When setting up
BUNDLE_GLOBAL_GEM_CACHE=1
it installs the gems correctly. In a CI environment you want to carry that cache over to a next build. When the next CI run happens (which contains only the cache folder from previous execution) the gems "install" correctly but when trying to execute the code it claims the gems with native extensions are missing the compiled extension/library.You can see an example here:
https://gitlab.com/gitlab-org/gitlab-development-kit/-/jobs/4117614795
Did you try upgrading rubygems & bundler?
Yes, I've tried using latest versions of both:
Post steps to reproduce the problem
I've tested this locally by setting:
And doing the following:
bundle install
bundle clean --force
bundle install
pg
)Which command did you run?
bundle install
rails console
What were you expecting to happen?
What actually happened?
If not included with the output of your command, run
bundle env
and paste the output belowEnvironment
Bundler Build Metadata
Bundler settings
Environment
Bundler Build Metadata
Bundler settings
The text was updated successfully, but these errors were encountered: