Skip to content

fix nightly lints surprise build breakage#51

Merged
pawelchcki merged 9 commits into
mainfrom
pawel/fix_nightly_lints_surprise_build_breakage
Sep 28, 2022
Merged

fix nightly lints surprise build breakage#51
pawelchcki merged 9 commits into
mainfrom
pawel/fix_nightly_lints_surprise_build_breakage

Conversation

@pawelchcki

@pawelchcki pawelchcki commented Sep 13, 2022

Copy link
Copy Markdown
Contributor

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

@pawelchcki pawelchcki force-pushed the pawel/fix_nightly_lints_surprise_build_breakage branch 3 times, most recently from 94f29a2 to dd4c73f Compare September 13, 2022 12:08
@pawelchcki pawelchcki force-pushed the pawel/fix_nightly_lints_surprise_build_breakage branch 2 times, most recently from 4560034 to a986cf0 Compare September 13, 2022 12:11
@pawelchcki pawelchcki force-pushed the pawel/fix_nightly_lints_surprise_build_breakage branch from a986cf0 to 167fbce Compare September 13, 2022 12:12
@pawelchcki pawelchcki force-pushed the pawel/fix_nightly_lints_surprise_build_breakage branch from c1fbbed to a9dfe92 Compare September 13, 2022 12:20
@pawelchcki pawelchcki marked this pull request as ready for review September 13, 2022 14:09
@pawelchcki pawelchcki requested a review from a team as a code owner September 13, 2022 14:09

@morrisonlevi morrisonlevi left a comment

Copy link
Copy Markdown
Contributor

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?

@pawelchcki

Copy link
Copy Markdown
Contributor Author

@morrisonlevi

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'd suggest we revisit its removal once we hit another false positive.

I've added stable version + improved caching.

~/.cargo/git/db/
~/.cargo/bin/
~/.cargo/.crates.toml
key: "v1-0.5.0"

Copy link
Copy Markdown
Contributor

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?

Copy link
Copy Markdown
Contributor Author

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

@pawelchcki pawelchcki merged commit 48ad681 into main Sep 28, 2022
@bantonsson bantonsson deleted the pawel/fix_nightly_lints_surprise_build_breakage branch March 7, 2024 07:15
ivoanjo pushed a commit that referenced this pull request Jun 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants