From: "kernelci.org bot" <bot@kernelci•org>
To: linux-next@vger•kernel.org
Subject: next/pending-fixes boot: 62 boots: 2 failed, 56 passed with 3 offline, 1 untried/unknown (v5.5-7780-g420617c9e573)
Date: Fri, 31 Jan 2020 08:39:23 -0800 (PST) [thread overview]
Message-ID: <5e34583b.1c69fb81.6f742.3f6a@mx.google.com> (raw)
next/pending-fixes boot: 62 boots: 2 failed, 56 passed with 3 offline, 1 untried/unknown (v5.5-7780-g420617c9e573)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.5-7780-g420617c9e573/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.5-7780-g420617c9e573/
Tree: next
Branch: pending-fixes
Git Describe: v5.5-7780-g420617c9e573
Git Commit: 420617c9e573e02af57c38d767b63ca4fe4461e2
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 46 unique boards, 15 SoC families, 21 builds out of 182
Boot Regressions Detected:
arm:
davinci_all_defconfig:
gcc-8:
dm365evm,legacy:
lab-baylibre-seattle: new failure (last pass: v5.5-5439-gb1111a46ce07)
exynos_defconfig:
gcc-8:
exynos5250-arndale:
lab-baylibre-seattle: new failure (last pass: v5.5-5439-gb1111a46ce07)
exynos5800-peach-pi:
lab-baylibre-seattle: new failure (last pass: v5.5-5439-gb1111a46ce07)
sunxi_defconfig:
gcc-8:
sun8i-h2-plus-orangepi-r1:
lab-baylibre: new failure (last pass: v5.5-5439-gb1111a46ce07)
Boot Failures Detected:
arm:
exynos_defconfig:
gcc-8:
exynos5250-arndale: 1 failed lab
exynos5800-peach-pi: 1 failed lab
Offline Platforms:
arm:
sunxi_defconfig:
gcc-8
sun5i-r8-chip: 1 offline lab
qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
davinci_all_defconfig:
gcc-8
dm365evm,legacy: 1 offline lab
---
For more info write to <info@kernelci•org>
reply other threads:[~2020-01-31 16:39 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=5e34583b.1c69fb81.6f742.3f6a@mx.google.com \
--to=bot@kernelci$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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