@Benjamin Bouvier as a heads up the Embark CI appears to be failing. It looks like it's been failing for quite some time and the failure at the beginning is at least different than the failure it has right now. I can't reproduce the failure myself locally, but are there perhaps configuration or environment variables set on the CI machine? For example is debuginfo enabled for release builds or something like that?
If you can log into the machine itself you can try running cargo +nightly config get -Z unstable-options
to print out what Cargo thinks its configuration is
hi! i don't work at Embark anymore, but maybe @Johan Andersson @Jake Shadle can take a look? (hi!)
Oops, just realized I forgot to respond to this (never use zulip). We no longer use the Mac machines for anything but running test binaries, so it's probably something just related to outdated cargo/rust/system deps, so hopefully a simple update will fix things. I'll take a look sometime this week.
Last updated: Dec 23 2024 at 13:07 UTC