You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
aarch64 being a tier-2 Rust architecture, both rustfmt and clippy are not available for the 2 aarch64 toochains (musl and glibc) that we use, since 1.36.0.
Nightly (2019-12-16) has those 2 available for aarch64 though.
We just updated our CI container Dockerfile toolchain to 1.39.0, but since our buildkite default scripts run clippy on aarch64, we can not switch to the newly built container. Potential solutions:
Use a fixed nightly toolchain (2019-12-16 for example) for the aarch64 CI container until the next stable release supports clippy for that architecture.
Skip clippy check from our default buildkite pipeline
The text was updated successfully, but these errors were encountered:
For rustfmt, we don't need to run it on both platforms. It will format all the code even if run only on x86_64. We can just remove the code from the pipeline. If that's the same for clippy, we can just remove clippy as well from the pipeline. What do you think?
aarch64
being a tier-2 Rust architecture, bothrustfmt
andclippy
are not available for the 2 aarch64 toochains (musl and glibc) that we use, since 1.36.0.Nightly (2019-12-16) has those 2 available for aarch64 though.
We just updated our CI container Dockerfile toolchain to 1.39.0, but since our buildkite default scripts run
clippy
on aarch64, we can not switch to the newly built container. Potential solutions:clippy
for that architecture.clippy
check from our default buildkite pipelineThe text was updated successfully, but these errors were encountered: