From: "kernelci.org bot" <bot@kernelci.org>
To: llvm@lists.linux.dev
Subject: next/master build: 221 builds: 19 failed, 202 passed (next-20221019)
Date: Wed, 19 Oct 2022 00:14:09 -0700 (PDT) [thread overview]
Message-ID: <634fa3c1.620a0220.5cf93.374e@mx.google.com> (raw)
next/master build: 221 builds: 19 failed, 202 passed (next-20221019)
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20221019/
Tree: next
Branch: master
Git Describe: next-20221019
Git Commit: a72b55bc981b62f7186600d06d1824f1d0612b27
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Built: 8 unique architectures
Build Failures Detected:
arm:
allmodconfig: (clang-16) FAIL
multi_v5_defconfig: (clang-16) FAIL
allmodconfig: (gcc-10) FAIL
imx_v4_v5_defconfig: (gcc-10) FAIL
multi_v4t_defconfig: (gcc-10) FAIL
multi_v5_defconfig: (gcc-10) FAIL
mxs_defconfig: (gcc-10) FAIL
rpc_defconfig: (gcc-10) FAIL
i386:
allmodconfig: (clang-16) FAIL
i386_defconfig+kselftest: (gcc-10) FAIL
mips:
decstation_64_defconfig: (gcc-10) FAIL
xway_defconfig: (gcc-10) FAIL
riscv:
allnoconfig: (clang-16) FAIL
defconfig+CONFIG_EFI=n: (clang-16) FAIL
defconfig: (gcc-10) FAIL
defconfig+debug: (gcc-10) FAIL
defconfig+kselftest: (gcc-10) FAIL
rv32_defconfig: (gcc-10) FAIL
x86_64:
allmodconfig: (clang-16) FAIL
---
For more info write to <info@kernelci.org>
next reply other threads:[~2022-10-19 7:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 7:14 kernelci.org bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-19 7:14 next/master build: 221 builds: 19 failed, 202 passed (next-20221019) kernelci.org bot
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=634fa3c1.620a0220.5cf93.374e@mx.google.com \
--to=bot@kernelci.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.