-
Notifications
You must be signed in to change notification settings - Fork 2k
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
CI failing with --no-default-features
#4441
Comments
Hello @curquiza 👋 I do not reproduce on branch release-v1.7.0 ( Commands I ran:
|
The problem is the CI is not working on Here is the CI manifest: https://github.com/meilisearch/meilisearch/blob/main/.github/workflows/test-suite.yml |
I re run it on |
4451: Fix nightly build r=dureuill a=dureuill # Pull Request ## Related issue Fixes #4441 ## What does this PR do? - Change imports following rust-lang/rust#117772 ## Note This one is going to be annoying a bit until the lint stabilizes: - We only get the warning on nightly, so we will discover them when it runs in the CI that uses the nightly compiler (not on regular PRs) - There's the case of `TryInto`/`TryFrom` traits. They have been added to the prelude in Rust edition 2021, so it means that `use`ing them is a warning on nightly for 2021 edition crates (most crates), but not `use`ing them is an error anywhere for 2018 Rust edition crates, such as `milli` Co-authored-by: Louis Dureuil <[email protected]>
Fixed by #4451 |
4453: Don't test on nightly r=dureuill a=dureuill # Pull Request ## Related issue Fixes #4441 better 😅 ## What does this PR do? - No longer run tests on nightly The motivation for this change is that we are now updating Rust at fixed points in time, and so no longer need nightly runs to ensure that a change won't get into stable and break our build at the worst possible moment. Co-authored-by: Louis Dureuil <[email protected]>
Describe the bug
CI runing with
cargo build --locked --release --no-default-features --all
fails onrelease-v1.7.0
Expected behavior
No CI failing
Screenshots
https://github.com/meilisearch/meilisearch/actions/runs/8045912784/job/21972108739
Meilisearch version:
Failing on
release-v1.7.0
.The text was updated successfully, but these errors were encountered: