Closed flba-eb closed 1 year ago
The failing test is not related to this change, see issue #511.
Could we pin the nightly version for that target or use build-std
instead?
I agree: using cargo {command} -Zbuild-std
is much more robust as a solution. It should still be removed eventually since we should be shipping a tier 2 target??? I don't know what's happening there.
Also this should be rebased on master just to make sure the CI run accurately reflects the current CI.
Though also, hmmm.
I wonder, is rustbot functional on this repo? Because this should really be
@rustbot ping fuchsia
RIP.
Ah, I see!
https://github.com/rust-lang/rust/pull/106429 renamed the target and the components are no longer shipped via that name.
Using x86_64-unknown-fuchsia
should resolve the problem here.
(More info: https://github.com/rust-lang/rust/pull/106636 re-added them to the supported targets, but it doesn't mean we can do rustup target add x86_64-fuchsia
, it seems.)
CI for Fuchsia seems to work now 😃 , but not all tests have been run (because of https://github.com/rust-lang/backtrace-rs/issues/511).
CI fails because there is no std lib available:
Availability monitor: https://rust-lang.github.io/rustup-components-history/