| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Mankirat Singh <mankiratsingh1315(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: ABI Compliance Checker GSoC Project |
| Date: | 2025-09-01 13:12:20 |
| Message-ID: | 411373F6-227B-4194-AEB4-82BF15D249AE@justatheory.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Aug 31, 2025, at 10:17, Mankirat Singh <mankiratsingh1315(at)gmail(dot)com> wrote:
> 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.
Thank you! I updated baza with the latest a couple days ago.
> Also, I think we can also have a configuration option for animal owners to toggle ABI change status on or off, thoughts?
Mabye? Might be worth waiting to see how much of an issue it is. If there is a failure a then a fix, it should turn green again. It might not be necessary.
What do you think, Hackers?
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Treat | 2025-09-01 13:28:33 | Re: pgbench - adding pl/pgsql versions of tests |
| Previous Message | Rahila Syed | 2025-09-01 13:05:55 | Re: Improve LWLock tranche name visibility across backends |