From: "kernelci.org bot" <bot@kernelci.org>
To: kernel-build-reports@lists.linaro.org,
kernelci-results@groups.io, chrome-platform@lists.linux.dev,
eballetbo@gmail.com, bleung@chromium.org, groeck@chromium.org,
pmalani@chromium.org
Subject: chrome-platform/for-kernelci build: 5 builds: 2 failed, 3 passed, 2 errors, 4 warnings (v6.8-rc1)
Date: Sun, 21 Jan 2024 20:08:40 -0800 (PST) [thread overview]
Message-ID: <65adea48.170a0220.9eaf9.06e0@mx.google.com> (raw)
chrome-platform/for-kernelci build: 5 builds: 2 failed, 3 passed, 2 errors, 4 warnings (v6.8-rc1)
Full Build Summary: https://kernelci.org/build/chrome-platform/branch/for-kernelci/kernel/v6.8-rc1/
Tree: chrome-platform
Branch: for-kernelci
Git Describe: v6.8-rc1
Git Commit: 6613476e225e090cc9aad49be7fa504e290dd33d
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git
Built: 3 unique architectures
Build Failures Detected:
x86_64:
x86_64_defconfig: (gcc-10) FAIL
x86_64_defconfig+x86-board: (gcc-10) FAIL
Errors and Warnings Detected:
arm64:
defconfig (gcc-10): 1 warning
defconfig+arm64-chromebook (gcc-10): 1 warning
arm:
x86_64:
x86_64_defconfig (gcc-10): 1 error, 1 warning
x86_64_defconfig+x86-board (gcc-10): 1 error, 1 warning
Errors summary:
2 security/security.c:810:2: error: ‘memcpy’ offset 32 is out of the bounds [0, 0] [-Werror=array-bounds]
Warnings summary:
2 security/security.c:810:2: warning: ‘memcpy’ offset 32 is out of the bounds [0, 0] [-Warray-bounds]
2 cc1: all warnings being treated as errors
================================================================================
Detailed per-defconfig build reports:
--------------------------------------------------------------------------------
defconfig (arm64, gcc-10) — PASS, 0 errors, 1 warning, 0 section mismatches
Warnings:
security/security.c:810:2: warning: ‘memcpy’ offset 32 is out of the bounds [0, 0] [-Warray-bounds]
--------------------------------------------------------------------------------
defconfig+arm64-chromebook (arm64, gcc-10) — PASS, 0 errors, 1 warning, 0 section mismatches
Warnings:
security/security.c:810:2: warning: ‘memcpy’ offset 32 is out of the bounds [0, 0] [-Warray-bounds]
--------------------------------------------------------------------------------
multi_v7_defconfig (arm, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
x86_64_defconfig (x86_64, gcc-10) — FAIL, 1 error, 1 warning, 0 section mismatches
Errors:
security/security.c:810:2: error: ‘memcpy’ offset 32 is out of the bounds [0, 0] [-Werror=array-bounds]
Warnings:
cc1: all warnings being treated as errors
--------------------------------------------------------------------------------
x86_64_defconfig+x86-board (x86_64, gcc-10) — FAIL, 1 error, 1 warning, 0 section mismatches
Errors:
security/security.c:810:2: error: ‘memcpy’ offset 32 is out of the bounds [0, 0] [-Werror=array-bounds]
Warnings:
cc1: all warnings being treated as errors
---
For more info write to <info@kernelci.org>
reply other threads:[~2024-01-22 4:08 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=65adea48.170a0220.9eaf9.06e0@mx.google.com \
--to=bot@kernelci.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=eballetbo@gmail.com \
--cc=groeck@chromium.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kernelci-results@groups.io \
--cc=pmalani@chromium.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 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.