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: 0 failed, 5 passed (v6.3-rc1-6-g14bb09b32f43)
Date: Mon, 10 Apr 2023 21:05:45 -0700 (PDT) [thread overview]
Message-ID: <6434dc99.170a0220.1a565.9e48@mx.google.com> (raw)
chrome-platform/for-kernelci build: 5 builds: 0 failed, 5 passed (v6.3-rc1-6-g14bb09b32f43)
Full Build Summary: https://kernelci.org/build/chrome-platform/branch/for-kernelci/kernel/v6.3-rc1-6-g14bb09b32f43/
Tree: chrome-platform
Branch: for-kernelci
Git Describe: v6.3-rc1-6-g14bb09b32f43
Git Commit: 14bb09b32f433c1c87d96732ad71442d03fd4e73
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git
Built: 3 unique architectures
================================================================================
Detailed per-defconfig build reports:
--------------------------------------------------------------------------------
defconfig (arm64, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
defconfig+arm64-chromebook (arm64, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
multi_v7_defconfig (arm, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
x86_64_defconfig (x86_64, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
x86_64_defconfig+x86-chromebook (x86_64, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
---
For more info write to <info@kernelci.org>
reply other threads:[~2023-04-11 4:05 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=6434dc99.170a0220.1a565.9e48@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox