On Fri, Apr 15, 2022 at 11:31 AM Junio C Hamano <gitster@xxxxxxxxx> wrote: > > Carlo Marcelo Arenas Belón <carenas@xxxxxxxxx> writes: > > > Fedora 36 is scheduled to be released in Apr 19th, but it includes > > a prerelease of gcc 12 that has known issues[1] with our codebase > > and therefore requires extra changes to not break a DEVELOPER=1 > > build. > > > > Lock the CI job to the current release image, and while at it rename > > the job to better reflect what it is currently doing, instead of its > > original objective. > > Please spell out what "original objective" is, why we are changing > the purpose of the target, and how such a change is justifiable. Will do in a reroll with the objective of "let's make the pedantic job more useful" but that is IMHO less of a priority and orthogonal to the objective of this series which was "let's avoid breaking our CI because of fedora's gcc updates". Original I had that done on top of ab/http-gcc-12-workaround (which fixes a real, albeit likely harmless bug that compiler was surfacing, and that will also break our CI in a few days) but after the feedback from this thread, think might be preferred and also less likely to conflict with current seen. Would that be reasonable, eventhough it is so late in the RC cycle? Carlo
