From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/pending-fixes boot: 254 boots: 3 failed, 245 passed with 6 offline (v5.4-rc8-85-g0632e899eb04)
Date: Mon, 18 Nov 2019 19:32:02 -0800 (PST) [thread overview]
Message-ID: <5dd36232.1c69fb81.c4dc8.6bbc@mx.google.com> (raw)
next/pending-fixes boot: 254 boots: 3 failed, 245 passed with 6 offline (v5.4-rc8-85-g0632e899eb04)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.4-rc8-85-g0632e899eb04/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.4-rc8-85-g0632e899eb04/
Tree: next
Branch: pending-fixes
Git Describe: v5.4-rc8-85-g0632e899eb04
Git Commit: 0632e899eb046db54d3b1c993811e0b1b7b90b04
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 96 unique boards, 27 SoC families, 28 builds out of 216
Boot Regressions Detected:
arm:
omap2plus_defconfig:
gcc-8:
am335x-boneblack:
lab-baylibre: failing since 1 day (last pass: v5.4-rc7-105-g01970a127dd4 - first fail: v5.4-rc7-306-gb1a61072f202)
Boot Failures Detected:
arm64:
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
meson-g12b-a311d-khadas-vim3: 1 failed lab
defconfig:
gcc-8:
msm8998-mtp: 1 failed lab
arm:
omap2plus_defconfig:
gcc-8:
am335x-boneblack: 1 failed lab
Offline Platforms:
arm:
sunxi_defconfig:
gcc-8
sun7i-a20-bananapi: 1 offline lab
multi_v7_defconfig:
gcc-8
bcm4708-smartrg-sr400ac: 1 offline lab
exynos5800-peach-pi: 1 offline lab
mt7623n-bananapi-bpi-r2: 1 offline lab
sun7i-a20-bananapi: 1 offline lab
exynos_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-11-19 3:32 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=5dd36232.1c69fb81.c4dc8.6bbc@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).