check-cocci is still a good idea -- perhaps as a cron job? But
doing it as part of our regular tests has just been confusing,
especially to volunteers who shouldn't have to become coccinelle
experts in order to get their patches through our CI.
Closes #40030.
check-spaces \
check-changes \
check-includes \
- shellcheck \
- check-cocci
+ shellcheck
need-chutney-path:
@if test ! -d "$$CHUTNEY_PATH"; then \
--- /dev/null
+ o Removed features:
+ - Our "check-local" test target no longer tries to use the Coccinelle
+ semantic patching tool parse all the C files. While it is a good idea
+ to try to make sure Coccinelle works on our C before we run a
+ Coccinelle patch, doing so on every test run has proven to be disruptive.
+ You can still run this tool manually with "make check-cocci". Closes
+ ticket 40030.