Re: Cleanup shadows variable warnings, round 1
Nazir Bilal Yavuz <byavuz81@gmail.com>
From: Bilal Yavuz <byavuz81@gmail.com>
To: Álvaro Herrera <alvherre@kurilemu.de>
Cc: Chao Li <li.evan.chao@gmail.com>, Peter Smith <smithpb2250@gmail.com>, Peter Eisentraut <peter@eisentraut.org>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-12-04T13:04:07Z
Lists: pgsql-hackers
Hi, On Thu, 4 Dec 2025 at 14:21, Álvaro Herrera <alvherre@kurilemu.de> wrote: > > On 2025-Dec-04, Chao Li wrote: > > > The motivation is that CF’s CI currently fails on shadow-variable warnings. > > If you touch a file like a.c, and that file already has a legacy shadowing > > issue, CI will still fail your patch even if your changes are correct. Then > > you’re forced to fix unrelated shadow-variable problems just to get a clean > > CI run. I’ve run into this myself, and it’s disruptive for both patch > > authors and reviewers. > > Hmm, maybe that should be turned off. It sounds seriously unhelpful. To test that I created this CI run [1], which edits the brin.c file. That file has a legacy shadowing issue but the CI did not fail. Could you please show an example CI run? [1] https://cirrus-ci.com/build/5444936843132928 -- Regards, Nazir Bilal Yavuz Microsoft