Re: ABI Compliance Checker GSoC Project
| От | David E. Wheeler |
|---|---|
| Тема | Re: ABI Compliance Checker GSoC Project |
| Дата | |
| Msg-id | 5DE83CB1-F756-4FF8-8FD9-FC40A1BD575B@justatheory.com обсуждение исходный текст |
| Ответ на | Re: ABI Compliance Checker GSoC Project (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: ABI Compliance Checker GSoC Project
|
| Список | pgsql-hackers |
Hi Tom, On Jan 10, 2026, at 15:34, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Now that we've more or less reduced the ABI compliance check to a > regular part of our process, it'd be good if baza were not a single > point of failure for making that check. I agree. > Has the final version of > the BF client change been published anywhere? How about setup > instructions for its infrastructure? Ideally you'd get Andrew to > incorporate all that into the standard release of the BF client. The PR[1] is pending Andrew’s bandwidth to look it over. But it’s easy to add it to an existing installation. From an earlierpost[2]: > 1. Download the module: > > ```sh > curl -LO https://raw.githubusercontent.com/MankiratSingh1315/pg-bf-client-code/refs/heads/abi-comp-check/PGBuild/Modules/ABICompCheck.pm > mv ABICompCheck.pm build-farm-path/PGBuild/Modules/ > ``` > > 2. Add it to `modules` in `build-farm.conf`, e.g., > > modules => [qw(TestUpgrade ABICompCheck)], > > 3. Install the abigail suite; I believe the Debian packages are `abigail-tools` and `libabigail0` > > I think that’s it. I use `run_branches.pl --run-all` to test all the current maintenance branches. It does not run againstmaster. It’s not too bad, since the module is fully-contained in a single .pm file. > (My immediate ambition is that there ought to be a 32-bit animal > doing ABI checks too, since the conditions are different than > on 64-bit.) That would be cool! D [1]: https://github.com/PGBuildFarm/client-code/pull/38 [2]: https://postgr.es/m/0C8DBCD6-7D68-4FD6-AE66-12B03AE7671B@justatheory.com
Вложения
В списке pgsql-hackers по дате отправления: