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.1-rc1-6-g18ffa74c2259)
Date: Mon, 31 Oct 2022 21:12:31 -0700 (PDT) [thread overview]
Message-ID: <63609caf.620a0220.bd35e.9c8e@mx.google.com> (raw)
chrome-platform/for-kernelci build: 5 builds: 0 failed, 5 passed (v6.1-rc1-6-g18ffa74c2259)
Full Build Summary: https://kernelci.org/build/chrome-platform/branch/for-kernelci/kernel/v6.1-rc1-6-g18ffa74c2259/
Tree: chrome-platform
Branch: for-kernelci
Git Describe: v6.1-rc1-6-g18ffa74c2259
Git Commit: 18ffa74c225988fdc907dd59051256d39816346c
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:[~2022-11-01 4:12 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=63609caf.620a0220.bd35e.9c8e@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.