Re: ABI Compliance Checker GSoC Project
От | Tom Lane |
---|---|
Тема | Re: ABI Compliance Checker GSoC Project |
Дата | |
Msg-id | 2220351.1757699597@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: ABI Compliance Checker GSoC Project (Álvaro Herrera <alvherre@kurilemu.de>) |
Список | pgsql-hackers |
=?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de> writes: > On 2025-Sep-12, Tom Lane wrote: >> My concern is that when we get a report, we might decide to apply >> some fix to remove the ABI delta, or we might decide it's intentional >> and/or harmless and leave the code as-is. > The solution I propose for this (which I have mentioned before) is to > allow for our source tree to carry exclusion files. The ABI checker > would refrain from turning red for any breaks that match what's in those > files. That seems substantially more complicated than just moving which commit is considered the baseline. It might be less reliable too: if the exclusions are written sloppily, they might hide problems we'd rather find out about. (I do not regard valgrind suppression files as a model of good engineering...) regards, tom lane
В списке pgsql-hackers по дате отправления: