-
Notifications
You must be signed in to change notification settings - Fork 10
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
fix nightly lints surprise build breakage #51
fix nightly lints surprise build breakage #51
Conversation
94f29a2
to
dd4c73f
Compare
4560034
to
a986cf0
Compare
a986cf0
to
167fbce
Compare
c1fbbed
to
a9dfe92
Compare
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 we're locked to v1.60 for now, maybe we should switch to latest stable instead of nightly? Or are there specific nightly features that we use or want to test against in CI?
Nightly has a few more lints, and I think it might be worth keeping, for now, since its track record seems somewhat good so far. I've added stable version + improved caching. |
~/.cargo/git/db/ | ||
~/.cargo/bin/ | ||
~/.cargo/.crates.toml | ||
key: "v1-0.5.0" |
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.
This number is magic to me; where does it come from?
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.
Its bundle licences v0.5.0 is the currently installed version. hmm maybe I should add a comment
Nightly builds that pull in latest lints daily, often cause us to chase broken tests.
In a few cases it turned out that the clippy checks were later removed - while we've lost time fixing code to keep the tests up to date.
This PR introduces adds latest "stable" clippy to be used as reference against latest nightly - and allows other builds in the matrix to finish if one of them fails.
Additionally it improves the caching on lints, and should reduce their execution time to seconds, instead of minutes