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 5 offline, 2 untried/unknown (v4.14.167)
Date: Thu, 23 Jan 2020 13:15:06 -0800 (PST) [thread overview]
Message-ID: <5e2a0cda.1c69fb81.eeb1d.4565@mx.google.com> (raw)
stable-rc/linux-4.14.y boot: 123 boots: 3 failed, 113 passed with 5 offline, 2 untried/unknown (v4.14.167)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.167/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.14.y/kernel/v4.14.167/
Tree: stable-rc
Branch: linux-4.14.y
Git Describe: v4.14.167
Git Commit: 8bac50406cca10a219aa899243d49c57ddaf7c5b
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 71 unique boards, 22 SoC families, 15 builds out of 191
Boot Regressions Detected:
arm:
davinci_all_defconfig:
gcc-8:
dm365evm,legacy:
lab-baylibre-seattle: new failure (last pass: v4.14.166-66-gbb5af942ee10)
sunxi_defconfig:
gcc-8:
sun4i-a10-cubieboard:
lab-baylibre-seattle: new failure (last pass: v4.14.166-66-gbb5af942ee10)
sun5i-r8-chip:
lab-baylibre-seattle: new failure (last pass: v4.14.166-66-gbb5af942ee10)
sun8i-a83t-bananapi-m3:
lab-clabbe: failing since 1 day (last pass: v4.14.166-56-g49153e6f7d26 - first fail: v4.14.166-66-gbb5af942ee10)
Boot Failures Detected:
arm64:
defconfig:
gcc-8:
meson-gxm-q200: 1 failed lab
arm:
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained: 1 failed lab
sunxi_defconfig:
gcc-8:
sun4i-a10-cubieboard: 1 failed lab
Offline Platforms:
arm:
sunxi_defconfig:
gcc-8
sun5i-r8-chip: 1 offline lab
multi_v7_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
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-23 21:15 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=5e2a0cda.1c69fb81.eeb1d.4565@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 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.