-
Notifications
You must be signed in to change notification settings - Fork 52
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
Multi-arch container builds are having some trouble #321
Comments
Hey @shaneutt, could I take this up? I’ve been experimenting with matrix builds and exploring this (https://github.com/taiki-e/upload-rust-binary-action)] I’ll raise a PR with my implementation by this week. |
the point of doing multi-arch builds for PRs is to verify that we aren't breaking compatibility with arm or x86. since our project relies on quite a bit of third party deps and libraries, its relatively easy to make a change that breaks on a platform. we can do a proper multi arch build for releases. |
@jokestax it would be great if you want to take a look at this, thank you! /assign @jokestax Keep in mind what @aryan9600 has said above and confer with him going forward. Particularly:
I do think we should probably only run these tests (only) on releases. If this ends up getting very difficult or nebulous for some reason though, please check back in here and we'll support you. |
hey @jokestax 👋 Just wanted to check in here: how are things going? Need any help? |
Hey @shaneutt ,sorry for not updating this,will make progress by this weekend |
No worries! Just wanted to check in. If you get blocked or need any help just let us know 🖖 |
Hi @shaneutt @aryan9600, I’ve updated the workflow to parallelize the image build process for AMD64 and ARM64. You can review the changes here: #342. Since push is set to false, I haven’t included a manifest in this update. I’m unsure if we should add it now or defer it for a future iteration. Let me know your thoughts! Looking forward to your feedback! |
Thank you! I'll take a look soon. Don't worry about pushing images, we have #339 to cover that. |
We recently updated our multi-arch container build, and since then I've seen quite a few failures that appear may be flakes and on success, I've seen it take as long as 70 minutes.
This isn't tenable to run on every PR, and each update for that PR. We need to evaluate a different strategy for container builds. Perhaps we can do the full multi-arch build on releases, but for PRs only do a basic x86_64 build?
The purpose of this issue is to explore a bit and see what potential solutions there are, pick one and implement it.
The text was updated successfully, but these errors were encountered: