From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org
Subject: stable-rc/linux-5.2.y boot: 143 boots: 2 failed, 132 passed with 8 offline, 1 untried/unknown (v5.2.8-157-g9e53d01dff58)
Date: Fri, 16 Aug 2019 10:41:47 -0700 (PDT) [thread overview]
Message-ID: <5d56eadb.1c69fb81.b4ebc.e8bb@mx.google.com> (raw)
stable-rc/linux-5.2.y boot: 143 boots: 2 failed, 132 passed with 8 offline, 1 untried/unknown (v5.2.8-157-g9e53d01dff58)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.2.y/kernel/v5.2.8-157-g9e53d01dff58/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-5.2.y/kernel/v5.2.8-157-g9e53d01dff58/
Tree: stable-rc
Branch: linux-5.2.y
Git Describe: v5.2.8-157-g9e53d01dff58
Git Commit: 9e53d01dff5817f759988ef384926ca6f6c5c47d
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 82 unique boards, 28 SoC families, 17 builds out of 209
Boot Regressions Detected:
arm:
qcom_defconfig:
gcc-8:
qcom-apq8064-cm-qs600:
lab-baylibre-seattle: failing since 1 day (last pass: v5.2.8 - first fail: v5.2.8-145-g2440e485aeda)
qcom-apq8064-ifc6410:
lab-baylibre-seattle: failing since 1 day (last pass: v5.2.8 - first fail: v5.2.8-145-g2440e485aeda)
Boot Failures Detected:
arm64:
defconfig:
gcc-8:
meson-gxbb-nanopi-k2: 1 failed lab
rk3399-firefly: 1 failed lab
Offline Platforms:
arm64:
defconfig:
gcc-8
apq8016-sbc: 1 offline lab
meson-gxbb-odroidc2: 1 offline lab
arm:
multi_v7_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
qcom-apq8064-ifc6410: 1 offline lab
sun5i-r8-chip: 1 offline lab
qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
qcom-apq8064-ifc6410: 1 offline lab
sunxi_defconfig:
gcc-8
sun5i-r8-chip: 1 offline lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-08-16 17:41 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=5d56eadb.1c69fb81.b4ebc.e8bb@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).