From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/pending-fixes boot: 239 boots: 2 failed, 225 passed with 11 offline, 1 untried/unknown (v5.4-rc7-190-g1b2a36d66d87)
Date: Wed, 13 Nov 2019 18:44:41 -0800 (PST) [thread overview]
Message-ID: <5dccbf99.1c69fb81.530e.8760@mx.google.com> (raw)
next/pending-fixes boot: 239 boots: 2 failed, 225 passed with 11 offline, 1 untried/unknown (v5.4-rc7-190-g1b2a36d66d87)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.4-rc7-190-g1b2a36d66d87/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.4-rc7-190-g1b2a36d66d87/
Tree: next
Branch: pending-fixes
Git Describe: v5.4-rc7-190-g1b2a36d66d87
Git Commit: 1b2a36d66d873784d653575f687f604fb6c6bc96
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 90 unique boards, 25 SoC families, 27 builds out of 215
Boot Failures Detected:
arm:
bcm2835_defconfig:
gcc-8:
bcm2837-rpi-3-b: 1 failed lab
arm64:
defconfig:
gcc-8:
msm8998-mtp: 1 failed lab
Offline Platforms:
arm:
sunxi_defconfig:
gcc-8
sun5i-r8-chip: 1 offline lab
sun7i-a20-bananapi: 1 offline lab
multi_v7_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
sun5i-r8-chip: 1 offline lab
sun7i-a20-bananapi: 1 offline lab
qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
arm64:
defconfig:
gcc-8
meson-axg-s400: 1 offline lab
sun50i-a64-pine64-plus: 1 offline lab
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8
meson-axg-s400: 1 offline lab
sun50i-a64-pine64-plus: 1 offline lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8
meson-axg-s400: 1 offline lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-11-14 2:44 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=5dccbf99.1c69fb81.530e.8760@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 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.