-
Notifications
You must be signed in to change notification settings - Fork 147
refactor(ci): consolidate clippy checks into one job #2695
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
Conversation
* only run clippy on stable version of rust
Another Call Out: I have addressed #2695 (comment). The original required job |
I ran my updated command and test it on my forked repo first: https://github.com/boquan-fang/s2n-quic/actions/runs/16380488388/job/46290742025. I checked and confirmed that clippy is running for all example crates:
It doesn't actually check any example crates, but after the latest commit, it does go in and check for all example crates:
|
* Combine all example into one workspace
b03d742
to
17eb9d3
Compare
The purpose of having a non-required beta clippy test was to give us a heads up that there were new Clippy lints coming down the road (assuming they were included in the beta). That gives us a chance to fix them before they start blocking the CI. |
Was anyone looking at this output though? It's not being looked at if it doesn't block PRs from getting merged. |
I agree with @maddeleine's comments. When a s2n-quic developer turns on auto merge after their PR is approved, they might not notice the clippy failure in the non-required run. This PR is one step towards a fully automated clippybot, which will fix clippy issue for us. If a new stable version is released and the new lints breaks our CI, the bot will let us know about the failure and fix it for us. Personally, I think that is a better mechanism than running a job on beta version. Moreover, even with the beta run, we still see new clippy failures which blocks our CI from time to time. That makes me wondering if the beta version run is actually helping. Let me know what you think about my take. |
This reverts commit 17eb9d3.
* We need to create a loop to run clippy
* parse all example crates and loop through them with clippy * add -D warnings to a job
* fix clippy failure in xdp crate
Call-outs: by serializing the clippy run in example crates, it will take more time for clippy to finish than before, since example clippy jobs were running in parallel previously. The consolidated clippy job will run for about 14 minutes. Such runtime seems reasonable, because there are other jobs that ran much slower than this. |
Release Summary:
Resolved issues:
related to #2643.
Description of changes:
As a first step to introduce the clippy bot, we should consolidate all clippy checks into one job. Currently, we have one clippy job running on the main crate, while other clippy jobs are scattering in other parts of
ci.yml
. This PR consolidate all of them together.Call-outs:
Testing:
We should use the CI to do the testing. We should check two things:
Run this in my personal forked repo: https://github.com/boquan-fang/s2n-quic/actions/runs/16380488388/job/46290742025. Manually check that all the jobs that were previously running are also running for this PR.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.