From: | Mankirat Singh <mankiratsingh1315(at)gmail(dot)com> |
---|---|
To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: ABI Compliance Checker GSoC Project |
Date: | 2025-08-31 14:17:41 |
Message-ID: | CAOtk82RS7njohZMTqo9rtj+vzEGxz1mJwXbvHJrwUwXtJwefzQ@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 27 Aug 2025 at 22:44, David E. Wheeler <david(at)justatheory(dot)com>
wrote:
> > I plan to work on false positives by adding abidiff suppression files
per branch (possibly managed in a community repo). I’d love to hear ideas
on this.
> Also, what rules should be put in place to make a build “fail” based on
what has changed? Right now, I believe, the results are simply reported
without a pass/fail. Would a failure status be useful, given some level of
change?
I have updated the module to report a failure status whenever any ABI
change is detected without specific conditions. For example, the image
attached from my local server gave a failure status on the ABICompCheck
step when comparing REL_17_1 with the head commit of REL_17_STABLE, as ABI
changes were found.
[image: image.png]
Also, I think we can also have a configuration option for animal owners to
toggle ABI change status on or off, thoughts?
Regards,
Mankirat
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-08-31 14:34:43 | Re: PG 18 relnotes and RC1 |
Previous Message | Vik Fearing | 2025-08-31 14:16:42 | Re: [PATCH] Add error_on_null() to produce an error if the input is null |