From: "kernelci.org bot" <bot@kernelci.org>
To: kernelci-results@groups.io, linux-kselftest@vger.kernel.org,
shuah@kernel.org
Subject: kselftest/next build: 8 builds: 0 failed, 8 passed, 3 errors (v6.1-rc1-17-g2dfb010d2aaf)
Date: Wed, 16 Nov 2022 10:49:06 -0800 (PST) [thread overview]
Message-ID: <637530a2.170a0220.8e0a3.3df0@mx.google.com> (raw)
kselftest/next build: 8 builds: 0 failed, 8 passed, 3 errors (v6.1-rc1-17-g2dfb010d2aaf)
Full Build Summary: https://kernelci.org/build/kselftest/branch/next/kernel/v6.1-rc1-17-g2dfb010d2aaf/
Tree: kselftest
Branch: next
Git Describe: v6.1-rc1-17-g2dfb010d2aaf
Git Commit: 2dfb010d2aafceeab23ccd502c77784006adedd7
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git
Built: 4 unique architectures
Errors Detected:
arm64:
defconfig+kselftest (clang-15): 1 error
defconfig+kselftest+arm64-chromebook (clang-15): 1 error
arm:
i386:
x86_64:
x86_64_defconfig+kselftest (clang-15): 1 error
Errors summary:
3 error: write on a pipe with no reader
================================================================================
Detailed per-defconfig build reports:
--------------------------------------------------------------------------------
defconfig+kselftest (arm64, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
defconfig+kselftest (arm64, clang-15) — PASS, 1 error, 0 warnings, 0 section mismatches
Errors:
error: write on a pipe with no reader
--------------------------------------------------------------------------------
defconfig+kselftest+arm64-chromebook (arm64, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
defconfig+kselftest+arm64-chromebook (arm64, clang-15) — PASS, 1 error, 0 warnings, 0 section mismatches
Errors:
error: write on a pipe with no reader
--------------------------------------------------------------------------------
i386_defconfig+kselftest (i386, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
multi_v7_defconfig+kselftest (arm, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
x86_64_defconfig+kselftest (x86_64, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
x86_64_defconfig+kselftest (x86_64, clang-15) — PASS, 1 error, 0 warnings, 0 section mismatches
Errors:
error: write on a pipe with no reader
---
For more info write to <info@kernelci.org>
reply other threads:[~2022-11-16 18:52 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=637530a2.170a0220.8e0a3.3df0@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