From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Philip Li <philip.li@intel.com>
Cc: kernel test robot <lkp@intel.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [gustavoars:testing/wfamnae-next20241104-inet-sock] BUILD REGRESSION 12b3f0eabce902acc13e01d76d9fd848474d4654
Date: Mon, 11 Nov 2024 20:48:04 -0600 [thread overview]
Message-ID: <8044b259-22e5-4f17-89c9-0706977c2593@embeddedor.com> (raw)
In-Reply-To: <ZzLAWrERdt0ijgpJ@rli9-mobl>
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@intel.com/
>
> 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
prev parent reply other threads:[~2024-11-12 2:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 10:10 kernel test robot
2024-11-12 2:29 ` Gustavo A. R. Silva
2024-11-12 2:41 ` Philip Li
2024-11-12 2:48 ` Gustavo A. R. Silva [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8044b259-22e5-4f17-89c9-0706977c2593@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=philip.li@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®