Re: [gustavoars:testing/wfamnae-next20241104-inet-sock] BUILD REGRESSION 12b3f0eabce902acc13e01d76d9fd848474d4654

[Gustavo A. R. Silva]

On 11/11/24 20:41, Philip Li wrote:
> On Mon, Nov 11, 2024 at 08:29:39PM -0600, Gustavo A. R. Silva wrote:
> > Hi!
> >
> > On 10/11/24 04:10, kernel test robot wrote:
> > > tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git testing/wfamnae-next20241104-inet-sock
> > > branch HEAD: 12b3f0eabce902acc13e01d76d9fd848474d4654  net: inet_sock.h: Avoid thousands of -Wflex-array-member-not-at-end warnings
> > >
> > > Error/Warning ids grouped by kconfigs:
> > >
> > > recent_errors
> > > |-- arm-allmodconfig
> > > |   `-- include-linux-build_bug.h:error:static-assertion-failed:struct-member-likely-outside-of-struct_group_tagged()
> > > |-- arm-allyesconfig
> > > |   `-- include-linux-build_bug.h:error:static-assertion-failed:struct-member-likely-outside-of-struct_group_tagged()
> > > |-- mips-allmodconfig
> > > |   `-- include-linux-build_bug.h:error:static-assertion-failed:struct-member-likely-outside-of-struct_group_tagged()
> > > |-- mips-allyesconfig
> > > |   `-- include-linux-build_bug.h:error:static-assertion-failed:struct-member-likely-outside-of-struct_group_tagged()
> > > |-- parisc-allmodconfig
> > > |   `-- include-linux-build_bug.h:error:static-assertion-failed:struct-member-likely-outside-of-struct_group_tagged()
> > > |-- parisc-allyesconfig
> > > |   `-- include-linux-build_bug.h:error:static-assertion-failed:struct-member-likely-outside-of-struct_group_tagged()
> > > `-- xtensa-allyesconfig
> > >       `-- include-linux-build_bug.h:error:static-assertion-failed:struct-member-likely-outside-of-struct_group_tagged()
> >
> > Which compiler was used GCC or Clang? Which version?
> >
> > Including more detailed logs for these Errors/Warnings
> > would be of great help if possible. :)
>
> Got it, this could be related to an earlier failure, would you take a look
> at https://lore.kernel.org/oe-kbuild-all/202410171308.VlSadp8v-lkp@xxxxxxxxx/
>
> Sorry that the link is not shown in this status report.

It's great that you could retrieve this link so quickly. Hopefully, this could
also be automated, thus including those links or adding more details about the
errors/warnings.

In any case, thanks a lot for your help, these builds are really helpful and
valuable! :)

--
Gustavo