From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org
Subject: stable-rc/linux-5.4.y boot: 167 boots: 1 failed, 158 passed with 3 offline, 5 untried/unknown (v5.4.29-28-gc1d6c1dff8f2)
Date: Wed, 01 Apr 2020 17:44:12 -0700 (PDT) [thread overview]
Message-ID: <5e85355c.1c69fb81.55d8b.c8df@mx.google.com> (raw)
stable-rc/linux-5.4.y boot: 167 boots: 1 failed, 158 passed with 3 offline, 5 untried/unknown (v5.4.29-28-gc1d6c1dff8f2)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.4.y/kernel/v5.4.29-28-gc1d6c1dff8f2/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-5.4.y/kernel/v5.4.29-28-gc1d6c1dff8f2/
Tree: stable-rc
Branch: linux-5.4.y
Git Describe: v5.4.29-28-gc1d6c1dff8f2
Git Commit: c1d6c1dff8f20567448ba39841abfe8be3037995
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 101 unique boards, 26 SoC families, 21 builds out of 199
Boot Regressions Detected:
arm:
qcom_defconfig:
gcc-8:
qcom-apq8064-cm-qs600:
lab-baylibre-seattle: failing since 53 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 17 days (last pass: v5.4.25 - first fail: v5.4.25-58-gc72f49ecd87b)
versatile_defconfig:
gcc-8:
versatile-pb:
lab-collabora: new failure (last pass: v5.4.29)
arm64:
defconfig:
gcc-8:
meson-axg-s400:
lab-baylibre-seattle: new failure (last pass: v5.4.29)
sun50i-a64-bananapi-m64:
lab-clabbe: new failure (last pass: v5.4.29)
Boot Failure Detected:
arm:
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained: 1 failed lab
Offline Platforms:
arm:
qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
multi_v7_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
arm64:
defconfig:
gcc-8
meson-axg-s400: 1 offline lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-04-02 0:44 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=5e85355c.1c69fb81.55d8b.c8df@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.