test: Remove vulture from ci, Remove some --min-confidence=60 unused code#34816
test: Remove vulture from ci, Remove some --min-confidence=60 unused code#34816maflcko wants to merge 6 commits intobitcoin:masterfrom
Conversation
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ReviewsSee the guideline for information on the review process.
If your review is incorrectly listed, please copy-paste ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
|
code review ACK fab5072 |
Went ahead and did this myself. I ran |
|
I see this locally? |
fa15057 to
fa90b21
Compare
Thx, removed all those lines as well. Let's see if lint CI passes ... edit: passed |
willcl-ark
left a comment
There was a problem hiding this comment.
ACK fa90b21
Changes LGTM.
Of course, removing this from CI does not prevent anyone from running it locally and removing dead code.
Well, its free to run on GHA so stuck it in my nightly repo at confidence level 100.
Could probably set it to run monthly at confidence=60 and have claude prune the output for false positives, but not sure there is enough demand/benefit.
Currently,
vultureis run with--min-confidence=100, which reduces its checks to dead code after control statements, which is nice, but not really a common nor severe issue. See the discussion in #34810 (comment) and commit 5c00536, which had to remove dead code manually.Reducing the confidence has shown to be too brittle/tedious in the past, so remove the tool for now from CI.
Of course, removing this from CI does not prevent anyone from running it locally and removing dead code.
Fixes #34810