From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org
Subject: stable-rc/linux-5.4.y boot: 165 boots: 2 failed, 153 passed with 5 offline, 5 untried/unknown (v5.4.41-2-ged1728340b22)
Date: Thu, 14 May 2020 16:30:15 -0700 (PDT) [thread overview]
Message-ID: <5ebdd487.1c69fb81.9cf74.12c4@mx.google.com> (raw)
stable-rc/linux-5.4.y boot: 165 boots: 2 failed, 153 passed with 5 offline, 5 untried/unknown (v5.4.41-2-ged1728340b22)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.4.y/kernel/v5.4.41-2-ged1728340b22/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-5.4.y/kernel/v5.4.41-2-ged1728340b22/
Tree: stable-rc
Branch: linux-5.4.y
Git Describe: v5.4.41-2-ged1728340b22
Git Commit: ed1728340b22cd2d0143fcc832c76ac40f409888
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 101 unique boards, 26 SoC families, 20 builds out of 200
Boot Regressions Detected:
arm:
bcm2835_defconfig:
gcc-8:
bcm2837-rpi-3-b:
lab-baylibre: new failure (last pass: v5.4.40-91-g132220af41e6)
qcom_defconfig:
gcc-8:
qcom-apq8064-cm-qs600:
lab-baylibre-seattle: failing since 96 days (last pass: v5.4.17-99-gbd0c6624a110 - first fail: v5.4.17-238-gbffcaa93483d)
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained:
lab-baylibre: failing since 36 days (last pass: v5.4.30-37-g40da5db79b55 - first fail: v5.4.30-39-g23c04177b89f)
versatile_defconfig:
gcc-8:
versatile-pb:
lab-collabora: new failure (last pass: v5.4.40-87-g4fdbdad79626)
Boot Failures Detected:
arm:
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained: 1 failed lab
bcm2835_defconfig:
gcc-8:
bcm2837-rpi-3-b: 1 failed lab
Offline Platforms:
arm:
multi_v7_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
qcom-apq8064-cm-qs600: 1 offline lab
stih410-b2120: 1 offline lab
qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
exynos_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-05-14 23:30 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=5ebdd487.1c69fb81.9cf74.12c4@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).