Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: "kernelci.org bot" <bot@kernelci.org>
To: kernelci-results@groups.io, linux-kselftest@vger.kernel.org,
	shuah@kernel.org
Subject: kselftest/next build: 4 builds: 2 failed, 2 passed, 2 errors, 4 warnings (v6.8-rc1-57-g5d94da7ff00e)
Date: Mon, 04 Mar 2024 23:56:12 -0800 (PST)	[thread overview]
Message-ID: <65e6d01c.170a0220.37829.69d3@mx.google.com> (raw)

kselftest/next build: 4 builds: 2 failed, 2 passed, 2 errors, 4 warnings (v6.8-rc1-57-g5d94da7ff00e)

Full Build Summary: https://kernelci.org/build/kselftest/branch/next/kernel/v6.8-rc1-57-g5d94da7ff00e/

Tree: kselftest
Branch: next
Git Describe: v6.8-rc1-57-g5d94da7ff00e
Git Commit: 5d94da7ff00ef45737a64d947e7ff45aca972782
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git
Built: 4 unique architectures

Build Failures Detected:

i386:
    i386_defconfig+kselftest: (gcc-10) FAIL

x86_64:
    x86_64_defconfig+kselftest: (gcc-10) FAIL

Errors and Warnings Detected:

arm64:
    defconfig+kselftest (gcc-10): 1 warning

arm:
    multi_v7_defconfig+kselftest (gcc-10): 1 warning

i386:
    i386_defconfig+kselftest (gcc-10): 1 error, 1 warning

x86_64:
    x86_64_defconfig+kselftest (gcc-10): 1 error, 1 warning

Errors summary:

    2    include/linux/fortify-string.h:57:29: error: ‘__builtin_memcpy’ offset 32 is out of the bounds [0, 0] [-Werror=array-bounds]

Warnings summary:

    2    include/linux/fortify-string.h:57:29: warning: ‘__builtin_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+kselftest (arm64, gcc-10) — PASS, 0 errors, 1 warning, 0 section mismatches

Warnings:
    include/linux/fortify-string.h:57:29: warning: ‘__builtin_memcpy’ offset 32 is out of the bounds [0, 0] [-Warray-bounds]

--------------------------------------------------------------------------------
i386_defconfig+kselftest (i386, gcc-10) — FAIL, 1 error, 1 warning, 0 section mismatches

Errors:
    include/linux/fortify-string.h:57:29: error: ‘__builtin_memcpy’ offset 32 is out of the bounds [0, 0] [-Werror=array-bounds]

Warnings:
    cc1: all warnings being treated as errors

--------------------------------------------------------------------------------
multi_v7_defconfig+kselftest (arm, gcc-10) — PASS, 0 errors, 1 warning, 0 section mismatches

Warnings:
    include/linux/fortify-string.h:57:29: warning: ‘__builtin_memcpy’ offset 32 is out of the bounds [0, 0] [-Warray-bounds]

--------------------------------------------------------------------------------
x86_64_defconfig+kselftest (x86_64, gcc-10) — FAIL, 1 error, 1 warning, 0 section mismatches

Errors:
    include/linux/fortify-string.h:57:29: error: ‘__builtin_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-03-05  7:56 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=65e6d01c.170a0220.37829.69d3@mx.google.com \
    --to=bot@kernelci.org \
    --cc=kernelci-results@groups.io \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@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