From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/pending-fixes boot: 228 boots: 0 failed, 206 passed with 20 offline, 2 untried/unknown (v5.2-rc5-374-gae1b7dafef4c)
Date: Wed, 19 Jun 2019 16:28:19 -0700 (PDT) [thread overview]
Message-ID: <5d0ac513.1c69fb81.33206.96d7@mx.google.com> (raw)
next/pending-fixes boot: 228 boots: 0 failed, 206 passed with 20 offline, 2 untried/unknown (v5.2-rc5-374-gae1b7dafef4c)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.2-rc5-374-gae1b7dafef4c/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.2-rc5-374-gae1b7dafef4c/
Tree: next
Branch: pending-fixes
Git Describe: v5.2-rc5-374-gae1b7dafef4c
Git Commit: ae1b7dafef4c037bad8a67077b0c0b90e772958c
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 84 unique boards, 24 SoC families, 20 builds out of 223
Offline Platforms:
arm:
sama5_defconfig:
gcc-8
at91-sama5d4_xplained: 1 offline lab
at91-sama5d4ek: 1 offline lab
qcom_defconfig:
gcc-8
qcom-apq8064-ifc6410: 1 offline lab
tegra_defconfig:
gcc-8
tegra30-beaver: 1 offline lab
multi_v7_defconfig:
gcc-8
alpine-db: 1 offline lab
at91-sama5d4_xplained: 1 offline lab
at91-sama5d4ek: 1 offline lab
qcom-apq8064-ifc6410: 1 offline lab
sun5i-r8-chip: 1 offline lab
tegra30-beaver: 1 offline lab
bcm2835_defconfig:
gcc-8
bcm2835-rpi-b: 1 offline lab
sunxi_defconfig:
gcc-8
sun5i-r8-chip: 1 offline lab
arm64:
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8
apq8016-sbc: 1 offline lab
juno-r2: 1 offline lab
defconfig:
gcc-8
apq8016-sbc: 1 offline lab
juno-r2: 1 offline lab
mt7622-rfb1: 1 offline lab
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8
apq8016-sbc: 1 offline lab
juno-r2: 1 offline lab
mt7622-rfb1: 1 offline lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-06-19 23:28 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=5d0ac513.1c69fb81.33206.96d7@mx.google.com \
--to=bot@kernelci.org \
--cc=linux-next@vger.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;
as well as URLs for NNTP newsgroup(s).