On Fri, Oct 17, 2025 at 3:11 PM Nathan Bossart <[email protected]> wrote: > Anything else? I suppose this idea is entirely dependent on the > maintainers of the abi-compliance-check code to adapt to it, so we'll need > buy-in from them, too.
That would require parsing the file and understanding that any compliance failures associated with a given commit should be suppressed. But that seems decidedly nontrivial to me. I can easily think of (admittedly somewhat contrived) scenarios where it's basically impossible to make this work due to transitive dependencies across commits. I suspect that any practical approach to solving this problem will have to involve ignore files that look somewhat like a Valgrind suppression file. It'll have to be based on symbol names, plus possibly a specific ABI breakage type. -- Peter Geoghegan
