-
-
Notifications
You must be signed in to change notification settings - Fork 253
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
bundler-cache with sassc leads to [BUG] Illegal instruction at 0x00007f9xxx FFI error #141
Comments
Do you have links to the logs (or the logs themselves), and could you share the image versions? The only thing I can imagine that could cause this, if it is not a bug of FFI or sassc, is that the OS image updated to a newer C++ runtime, that might not be binary compatible (C ABI is guaranteed compatible IIRC, but C++ might not). I don't there is anything this action can do, this is either a change in the image by actions/virtual-environments or a bug in FFI or sassc. |
We could potentially include the image version in the cache key potentially, if that is helpful to fix this. |
I'm facing this problem since yesterday and I'm yet to find the proper solution to overcome it and still make use of the
Based on this upstream report, my understanding is that by default After clicking on the
In my specific use case, caching the portable version of the dependency, even if being a bit slower than the CPU-optimized one, would be better as the time took by |
@myhro Thank you for the details, that makes sense, I was also thinking that
How do you do that?
More of a workaround, but for the purpose of testing, you could add a dependency on some new gem, and change its version, and each will have a different cache. |
Potentially we could cache per CPU, but I wonder how many different CPUs there are for GitHub-hosted runners. |
It seems sassc 2.3.0+ already default to false for |
I was trying to have a I can confirm that the cached version worked for the older |
* # CI: try and cache the bundle between builds It currently takes ~5 minutes of compute time per job to do this. * # update sassc, to try and avoid CPU model-specific issues ref: ruby/setup-ruby#141
I ran into a bug where loading sassc leads to a ffi error. At first, the following action setup ran fine, however, after removing installation of bundler and the extra bundle install step, all subsequent runs of the actions failed, because of an illegal instruction in libffi. The error occurred in the db setup step. This seems to be the case because there is a non portable cached binary for sassc in the bundler cache.
Removing the bundler-cache fixed my pipeline.
Action setup:
Error:
The text was updated successfully, but these errors were encountered: