-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add cargo check+test for minimal-versions in CI #44
Conversation
.github/workflows/ci.yml
Outdated
- if: matrix.rust == 'nightly' | ||
run: | | ||
cargo +nightly update -Z minimal-versions | ||
cargo check --all-features --verbose --all-targets |
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.
Given that this is basically just a Will It Compile test, I suppose adding the --tests
(and possibly --examples
) options to this cargo check
and dropping the cargo test
below will be sufficient and save some cycles.
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.
The separate check
is indeed not super useful, though separate build
and test
is convenient to quickly spot where things go wrong. (Note that this was inspired by the ci.yml in the domain crate, so we might want to have a look at that one as well).
On saving cycles, it might actually make more sense to get rid of the beta/nightly runs.
…t-in-ci' into minimal-version-test-in-ci
This PR adds a CI job testing whether the minimal versions as specified in Cargo.toml actually compile and pass the unit tests.