-
Notifications
You must be signed in to change notification settings - Fork 379
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
Forward Cargo exit code #775
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. A simple test shows it works as desired, and properly returns the error code as if cargo has run it.
bors r+ (This might actually fail due to unrelated issues, but this would be due to secretly failing unittests that we currently think are passing: or, this PR is a really good thing). |
775: Forward Cargo exit code r=Alexhuszagh a=Jules-Bertholet Forward Cargo's exit code. For example, if `cargo test` returns a non-zero exit code due to a failing test, `cross` will also return a non-zero exit code. Co-authored-by: Jules Bertholet <[email protected]>
Build failed: |
@Emilgardis Can you merge this manually? Only failing test is |
we have xargo for a reason, making it use nightly would fix it, no? |
Yes it should. Let me test locally first. |
Added `build-std` flag to CI, so for targets that support `std` but are tier 3 targets, we can use the experimental `build-std` support to ensure they build. Also patches linking on dragonfly to ensure we use `libgcc_s` instead of `libgcc_pic`, which no longer exists. We just create a symlink for that purpose. Necessary to merge cross-rs#775.
Added `build-std` flag to CI, so for targets that support `std` but are tier 3 targets, we can use the experimental `build-std` support to ensure they build. Also patches linking on dragonfly to ensure we use `libgcc_s` instead of `libgcc_pic`, which no longer exists. We just create a symlink for that purpose. Necessary to merge cross-rs#775.
Added `build-std` flag to CI, so for targets that support `std` but are tier 3 targets, we can use the experimental `build-std` support to ensure they build. Also patches linking on dragonfly to ensure we use `libgcc_s` instead of `libgcc_pic`, which no longer exists. We just create a symlink for that purpose. Necessary to merge cross-rs#775.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bors r+
775: Forward Cargo exit code r=Emilgardis a=Jules-Bertholet Forward Cargo's exit code. For example, if `cargo test` returns a non-zero exit code due to a failing test, `cross` will also return a non-zero exit code. 776: Bug fix for dragonfly and CI tests. r=Emilgardis a=Alexhuszagh Added `build-std` flag to CI, so for targets that support `std` but are tier 3 targets, we can use the experimental `build-std` support to ensure they build. Also patches linking on dragonfly to ensure we use `libgcc_s` instead of `libgcc_pic`, which no longer exists. We just create a symlink for that purpose. Necessary to merge #775. Co-authored-by: Jules Bertholet <[email protected]> Co-authored-by: Alex Huszagh <[email protected]>
bors r- |
Canceled. |
Added `build-std` flag to CI, so for targets that support `std` but are tier 3 targets, we can use the experimental `build-std` support to ensure they build. Also patches linking on dragonfly to ensure we use `libgcc_s` instead of `libgcc_pic`, which no longer exists. We just create a symlink for that purpose. This also adds `build-std` detection into Rust, so we don't have to provide it manually. It allows use to avoid using `xargo` when possible. Necessary to merge cross-rs#775. Closes cross-rs#692.
Added `build-std` flag to CI, so for targets that support `std` but are tier 3 targets, we can use the experimental `build-std` support to ensure they build. Also patches linking on dragonfly to ensure we use `libgcc_s` instead of `libgcc_pic`, which no longer exists. We just create a symlink for that purpose. This also adds `build-std` detection into Rust, so we don't have to provide it manually. It allows use to avoid using `xargo` when possible. Necessary to merge cross-rs#775. Closes cross-rs#692.
Added `build-std` flag to CI, so for targets that support `std` but are tier 3 targets, we can use the experimental `build-std` support to ensure they build. Also patches linking on dragonfly to ensure we use `libgcc_s` instead of `libgcc_pic`, which no longer exists. We just create a symlink for that purpose. This also adds `build-std` detection into Rust, so we don't have to provide it manually. It allows use to avoid using `xargo` when possible. Necessary to merge cross-rs#775.
776: Bug fix for dragonfly and CI tests. r=Emilgardis a=Alexhuszagh Added `build-std` flag to CI, so for targets that support `std` but are tier 3 targets, we can use the experimental `build-std` support to ensure they build. Also patches linking on dragonfly to ensure we use `libgcc_s` instead of `libgcc_pic`, which no longer exists. We just create a symlink for that purpose. Necessary to merge #775. Co-authored-by: Alex Huszagh <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
bors r=Alexhuszagh,Emilgardis
Build succeeded: |
Added `build-std` flag to CI, so for targets that support `std` but are tier 3 targets, we can use the experimental `build-std` support to ensure they build. Also patches linking on dragonfly to ensure we use `libgcc_s` instead of `libgcc_pic`, which no longer exists. We just create a symlink for that purpose. This also adds `build-std` detection into Rust, so we don't have to provide it manually. It allows use to avoid using `xargo` when possible. Necessary to merge cross-rs#775.
Forward Cargo's exit code. For example, if
cargo test
returns a non-zero exit code due to a failing test,cross
will also return a non-zero exit code.