Closed justsmth closed 1 year ago
Build failed:
bors retry
cargo deny got stuck on network operations, unclear why
Build succeeded!
The publicly hosted instance of bors-ng is deprecated and will go away soon.
If you want to self-host your own instance, instructions are here. For more help, visit the forum.
If you want to switch to GitHub's built-in merge queue, visit their help page.
note that this won't build the docker image using the normal workflows, this due to some images failing, see #1208
thats the reason for me including the label no-ci-targets
I've manually started a check which should build and publish the changes, https://github.com/cross-rs/cross/actions/runs/5580937512
For Linux on the PowerPC-64 little-endian architecture, the output of
uname -m
is "ppc64le", which should align with the value used forCMAKE_SYSTEM_PROCESSOR
. This change updates the Docker image used forpowerpc64le-unknown-linux-gnu
with an appropriate default value forCROSS_CMAKE_SYSTEM_PROCESSOR
.This was found while investigating a CI failure on a PR supporting cross-compilation to powerpc64le.