public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: CKI Project <cki-project@redhat.com>
Cc: llvm@lists.linux.dev
Subject: Re: ❌ FAIL: Test report for kernel 5.15.0-rc1 (mainline.kernel.org-clang, 80be5998)
Date: Wed, 15 Sep 2021 11:28:32 -0700	[thread overview]
Message-ID: <YUI7UIZvrsfMO716@archlinux-ax161> (raw)
In-Reply-To: <cki.F1734A8D11.3SEIGX3SIL@redhat.com>

On Wed, Sep 15, 2021 at 06:24:13PM -0000, CKI Project wrote:
> 
> Hello,
> 
> We ran automated tests on a recent commit from this kernel tree:
> 
>        Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>             Commit: 80be5998ad63 - tools/bootconfig: Define memblock_free_ptr() to fix build error
> 
> The results of these automated tests are provided below.
> 
>     Overall result: FAILED (see details below)
>              Merge: OK
>            Compile: FAILED
>  Selftests compile: OK
> 
> All kernel binaries, config files, and logs are available for download here:
> 
>   https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/09/15/371395708
> 
> We attempted to compile the kernel for multiple architectures, but the compile
> failed on one or more architectures:
> 
>             x86_64: FAILED (see build-x86_64.log.xz attachment)

00:25:26 drivers/infiniband/hw/qib/qib_sysfs.c:413:1: error: static_assert expression is not an integral constant expression

We have a pending solution:

https://github.com/ClangBuiltLinux/linux/issues/1452
https://lore.kernel.org/r/0-v1-1b789bd4dbd4+14b16-clang-fix_jgg@nvidia.com/
https://git.kernel.org/rdma/rdma/c/3110b942d36b961858664486d72f815d78c956c3

Cheers,
Nathan

      reply	other threads:[~2021-09-15 18:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15 18:24 ❌ FAIL: Test report for kernel 5.15.0-rc1 (mainline.kernel.org-clang, 80be5998) CKI Project
2021-09-15 18:28 ` Nathan Chancellor [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=YUI7UIZvrsfMO716@archlinux-ax161 \
    --to=nathan@kernel.org \
    --cc=cki-project@redhat.com \
    --cc=llvm@lists.linux.dev \
    /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