From: "kernelci.org bot" <bot@kernelci.org>
To: will@kernel.org, catalin.marinas@arm.com,
linux-arm-kernel@lists.infradead.org,
kernel-build-reports@lists.linaro.org,
kernelci-results@groups.io
Subject: arm64/for-kernelci build: 2 builds: 1 failed, 1 passed, 1 error, 1 warning (v6.2-rc3-17-g358a161a6a9e)
Date: Tue, 10 Jan 2023 00:22:57 -0800 (PST) [thread overview]
Message-ID: <63bd2061.630a0220.d89da.977f@mx.google.com> (raw)
arm64/for-kernelci build: 2 builds: 1 failed, 1 passed, 1 error, 1 warning (v6.2-rc3-17-g358a161a6a9e)
Full Build Summary: https://kernelci.org/build/arm64/branch/for-kernelci/kernel/v6.2-rc3-17-g358a161a6a9e/
Tree: arm64
Branch: for-kernelci
Git Describe: v6.2-rc3-17-g358a161a6a9e
Git Commit: 358a161a6a9e854032422818e1e22b66c3208999
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
Built: 1 unique architecture
Build Failure Detected:
arm64:
allmodconfig: (gcc-10) FAIL
Errors and Warnings Detected:
arm64:
allmodconfig (gcc-10): 1 error, 1 warning
Errors summary:
1 include/linux/fortify-string.h:57:29: error: argument 2 null where non-null expected [-Werror=nonnull]
Warnings summary:
1 cc1: all warnings being treated as errors
================================================================================
Detailed per-defconfig build reports:
--------------------------------------------------------------------------------
allmodconfig (arm64, gcc-10) — FAIL, 1 error, 1 warning, 0 section mismatches
Errors:
include/linux/fortify-string.h:57:29: error: argument 2 null where non-null expected [-Werror=nonnull]
Warnings:
cc1: all warnings being treated as errors
--------------------------------------------------------------------------------
defconfig (arm64, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
---
For more info write to <info@kernelci.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2023-01-10 8:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=63bd2061.630a0220.d89da.977f@mx.google.com \
--to=bot@kernelci.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kernelci-results@groups.io \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).