Re: breaking modules

From: Eugene Grosbein <eugen_at_grosbein.net>
Date: Fri, 29 Apr 2022 18:43:22 UTC
29.04.2022 21:49, Ed Maste wrote:

> On Thu, 28 Apr 2022 at 11:28, Julian H. Stacey <jhs@berklix.com> wrote:
>>
>> but that's crude. It's nice to be able to build most modules ready
>> in case wanted later, so how about a DUDS env. mechanism like ports/ ?
> 
> I'd rather not add additional complexity to our build infrastructure
> to address a situation that shouldn't exist. Modules should build &
> function on an ongoing basis (and, I believe they generally do). CI
> doesn't report any issues on either stable branch or main at present.

Unfortunately, CI does not catch stand-alone module build failures,
out of kernel build directory.

For example:

if_em		https://cgit.freebsd.org/src/commit/?id=c0460cf2e42d2819c1f191a1d6e1b3dc0c7ea010
if_epair	https://cgit.freebsd.org/src/commit/?id=7a382e744b0b0ba9b51dc34bfa0cd1515f744f25
linuxkpi	https://cgit.freebsd.org/src/commit/?id=f5a2e7b0e8483bf51519046fd149a6a31acef6b1