git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 2/2] ci: bump ubuntu image version for static-analysis job

From
Patrick Steinhardt <ps@pks.im>
Date
Aug 10, 2026, 05:38 UTC
Message-ID
<anlj3kdAfOh8OnNR@pks.im>
In-Reply-To
<xmqq8q6hgb2m.fsf@gitster.g>
On Fri, Aug 07, 2026 at 09:16:49AM -0700, Junio C Hamano wrote:
Show 24 quoted lines
> Patrick Steinhardt <ps@pks.im> writes:
> 
> > They'd of course require a bit of a deeper look, but that could be
> > another way to speed up Coccinelle for us. Even though I cannot say for
> > sure by how much, I didn't give it a test.
> 
> Another benefit is that it would reduce the programmer's burden, as
> it is not immediately apparent which rules are still relevant.
> 
> I wonder if we can easily define the exit criteria when we introduce
> a new rule and document them, immediately next to the rules.
> 
> You said "refs, object_id, the_repository, ... all look like we have
> long done with the migrations"; in retrospect, would it have been
> easily doable for those who introduced these rules to describe how
> we would declare "now migration is done"?  If so, perhaps a good
> step forward may be to update tools/coccinelle/README to add such a
> rule.
> 
>     ... goes and looks ...
> 
> The readme file clearly states that transformations needed for
> migrations are *not* regularly run.  Is it possible that we have
> these rules you mentioned misclassified?

For all I can see, both our Makefile and Meson simply take all Coccinelle files we have, concatenate and run those rules against our whole codebase. So I don't see any kind of classification at all?

Ah, no, you're right. We have the ".pending" suffix that we do treat special. We only have a single one of those with "config_fn_ctx". Arguably, many of the others should've been classified as pending, too. But I think it's quite easy to miss that we even treat these kinds of files special.

Taking a step back, I do have to wonder whether the Cocci files have been adding any kind of value in the first place. I myself introduced some of them in contexts where I made sweeping changes to our APIs, so that any in-flight topics can be trivially adjusted via Coccinelle. But I very much doubt that anyone ever used those to adapt their in-flight patch series at all.

So maybe we should just not do that anymore?
Patrick
Previous: Junio C HamanoNext: Junio C Hamano
Message 6 of 13 in “bump static-analysis ci image version”
  1. 0/2 bump static-analysis ci image versionJeff King, Jul 26, 2026
  2. 1/2 bloom: silence CHECK_ASSERTION_SIDE_EFFECTS false positiveJeff King, Jul 26, 2026
  3. 2/2 ci: bump ubuntu image version for static-analysis jobJeff King, Jul 26, 2026
  4. Patrick SteinhardtAug 7, 2026
  5. Junio C HamanoAug 7, 2026
  6. Patrick SteinhardtAug 10, 2026
  7. Junio C HamanoAug 10, 2026
  8. Patrick SteinhardtAug 11, 2026
  9. Jeff KingSep 5, 2026
  10. Elijah NewrenAug 7, 2026
  11. SZEDER GáborAug 8, 2026
  12. Jeff KingSep 5, 2026
  13. Junio C HamanoJul 26, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.