-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Broken 32-bits CI when using 0.35.0 #9463
Comments
I guess we no longer actually run a 32 bit CI? Or how did this remain undetected? FWIW I wouldn't be too outraged about dropping 32bits x86 support, most operating systems did that already. (We need to keep/improve 32bits ARM support though). |
Eventual 32bits ARM is the main reason I want to keep 32 bits support. Not sure yet why it went undetected the tagged release has a smoke test over the CI with the recent 32 bits build https://circleci.com/workflow-run/d70808f1-dc6d-46b6-91af-50c5e56dbd27 |
The underlying cause is that LibC.stat is not working on 32 bits environment when the path refers to mounted volume (like the docker mounted volume used to share the working copy in the ci, or vagrant shared file). This is seems to be an old issue cause it happens with older compilers also. |
I wonder if it's related to that large file support issue for arm... |
How about kubo@9442927 (#9297 (comment))? It fixes |
That seems to fix the issue of stat in docker and vagrant 32 bits. So 👍 . Yet the #9466 changes are still valid since we unintentionally changed the compiler flags on some specs. |
While trying to upgrade the CI to prepare it for 1.0.0-dev using 0.35.0 I stumbed on some failures that went undetected until the release in the 32-bits arch.
https://circleci.com/gh/crystal-lang/crystal/48093
Using crystallang/crystal:0.35.0-i386-build docker image against 0.35.0 tag.
The text was updated successfully, but these errors were encountered: