-
Notifications
You must be signed in to change notification settings - Fork 10
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
Tier 1 goal: Test Rust natively on Arm with Travis CI #34
Comments
CC @pietroalbini do you have any opinion on this? |
Hello @hug-dev! We're already talking with people from ARM about promoting aarch64 to Tier 1, but we don't have news to share just yet. Also, having CI available is just a small part of what makes a target tier 1: we had a design meeting a few weeks ago about writing a policy on what's required for a tier 1 promotion, and we expect that policy to be converted into an RFC soon. |
Great, thanks for the pointers! |
Hi @pietroalbini, any updates to share here? 🙂 |
We're currently investigating setting up CI for AArch64, but there is no official news to share yet. |
Not needed anymore since |
Hi All!
I posted my question about this topic on the Rust forum as well.
In a nutshell, as Travis CI now supports native builds on Arm64, it could be a good opportunity to set up a job on it running Rust CI tests on the
aarch64-unknown-linux-gnu
target.If it is possible for Rust CI infrastructure to have both Azure and Travis CI systems and if all tests run successfully on
aarch64-unknown-linux-gnu
target this could mean the promotion of this target as Tier 1.@parched also told me that there were other CI systems like codefresh that were offering Arm builds.
Last time I checked, all tests were passing but the variable arguments ones and this is addressed by @parched at rust-lang/rust#62207
The text was updated successfully, but these errors were encountered: