Skip to content
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

Merged
merged 2 commits into from
Jun 10, 2022
Merged

Conversation

Jules-Bertholet
Copy link
Contributor

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.

@Jules-Bertholet Jules-Bertholet requested a review from a team as a code owner June 9, 2022 17:04
Copy link
Contributor

@Alexhuszagh Alexhuszagh left a 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.

@Alexhuszagh
Copy link
Contributor

Alexhuszagh commented Jun 9, 2022

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).

bors bot added a commit that referenced this pull request Jun 9, 2022
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]>
@bors
Copy link
Contributor

bors bot commented Jun 9, 2022

Build failed:

@Alexhuszagh
Copy link
Contributor

@Emilgardis Can you merge this manually? Only failing test is dragonfly, which is because it's a tier 3 target and we shouldn't be running tests on it. I'll submit a CI PR for this later.

@Emilgardis
Copy link
Member

we have xargo for a reason, making it use nightly would fix it, no?

@Alexhuszagh
Copy link
Contributor

we have xargo for a reason, making it use nightly would fix it, no?

Yes it should. Let me test locally first.

Alexhuszagh added a commit to Alexhuszagh/cross that referenced this pull request Jun 9, 2022
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.
Alexhuszagh added a commit to Alexhuszagh/cross that referenced this pull request Jun 9, 2022
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.
Alexhuszagh added a commit to Alexhuszagh/cross that referenced this pull request Jun 9, 2022
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.
Copy link
Member

@Emilgardis Emilgardis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bors r+

bors bot added a commit that referenced this pull request Jun 9, 2022
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]>
@Emilgardis
Copy link
Member

bors r-

@bors
Copy link
Contributor

bors bot commented Jun 9, 2022

Canceled.

Alexhuszagh added a commit to Alexhuszagh/cross that referenced this pull request Jun 10, 2022
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.
Alexhuszagh added a commit to Alexhuszagh/cross that referenced this pull request Jun 10, 2022
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.
Alexhuszagh added a commit to Alexhuszagh/cross that referenced this pull request Jun 10, 2022
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.
bors bot added a commit that referenced this pull request Jun 10, 2022
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]>
Copy link
Member

@Emilgardis Emilgardis left a 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

@bors
Copy link
Contributor

bors bot commented Jun 10, 2022

Build succeeded:

@bors bors bot merged commit 23fd0af into cross-rs:main Jun 10, 2022
@Jules-Bertholet Jules-Bertholet deleted the forward-exit-code branch June 10, 2022 13:00
Alexhuszagh added a commit to Alexhuszagh/cross that referenced this pull request Jun 10, 2022
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.
@Emilgardis Emilgardis added this to the v0.2.2 milestone Jun 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants