From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org
Subject: stable-rc/linux-4.14.y boot: 123 boots: 3 failed, 113 passed with 6 offline, 1 untried/unknown (v4.14.160)
Date: Sat, 21 Dec 2019 09:01:54 -0800 (PST) [thread overview]
Message-ID: <5dfe5002.1c69fb81.88a14.62ab@mx.google.com> (raw)
stable-rc/linux-4.14.y boot: 123 boots: 3 failed, 113 passed with 6 offline, 1 untried/unknown (v4.14.160)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.160/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.14.y/kernel/v4.14.160/
Tree: stable-rc
Branch: linux-4.14.y
Git Describe: v4.14.160
Git Commit: e1f7d50ae3a3ec342e87a9b1ce6787bfb8b3c08b
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 72 unique boards, 22 SoC families, 16 builds out of 201
Boot Regressions Detected:
arm:
davinci_all_defconfig:
gcc-8:
dm365evm,legacy:
lab-baylibre-seattle: new failure (last pass: v4.14.159-37-g838b72b47f7e)
multi_v7_defconfig:
gcc-8:
sun8i-a83t-bananapi-m3:
lab-clabbe: new failure (last pass: v4.14.159-37-g838b72b47f7e)
versatile_defconfig:
gcc-8:
versatile-pb:
lab-collabora: new failure (last pass: v4.14.158-275-g0ddb1a505fdb)
Boot Failures Detected:
arm64:
defconfig:
gcc-8:
meson-gxm-q200: 1 failed lab
arm:
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained: 1 failed lab
multi_v7_defconfig:
gcc-8:
sun8i-a83t-bananapi-m3: 1 failed lab
Offline Platforms:
arm:
multi_v7_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
stih410-b2120: 1 offline lab
sun7i-a20-bananapi: 1 offline lab
davinci_all_defconfig:
gcc-8
dm365evm,legacy: 1 offline lab
sunxi_defconfig:
gcc-8
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-12-21 17:01 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=5dfe5002.1c69fb81.88a14.62ab@mx.google.com \
--to=bot@kernelci.org \
--cc=stable@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).