From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org
Subject: stable-rc/linux-4.19.y boot: 136 boots: 1 failed, 130 passed with 3 offline, 2 untried/unknown (v4.19.113-97-gaa90b785f040)
Date: Tue, 31 Mar 2020 09:04:09 -0700 (PDT) [thread overview]
Message-ID: <5e8369f9.1c69fb81.5fe9b.8cc5@mx.google.com> (raw)
stable-rc/linux-4.19.y boot: 136 boots: 1 failed, 130 passed with 3 offline, 2 untried/unknown (v4.19.113-97-gaa90b785f040)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.19.113-97-gaa90b785f040/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.19.y/kernel/v4.19.113-97-gaa90b785f040/
Tree: stable-rc
Branch: linux-4.19.y
Git Describe: v4.19.113-97-gaa90b785f040
Git Commit: aa90b785f0405d6a6780862cf951250a09e58af6
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 82 unique boards, 22 SoC families, 19 builds out of 206
Boot Regressions Detected:
arm:
qcom_defconfig:
gcc-8:
qcom-apq8064-cm-qs600:
lab-baylibre-seattle: failing since 51 days (last pass: v4.19.101 - first fail: v4.19.102-96-g0632821fe218)
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained:
lab-baylibre: failing since 18 days (last pass: v4.19.108-87-g624c124960e8 - first fail: v4.19.109)
arm64:
defconfig:
gcc-8:
meson-axg-s400:
lab-baylibre-seattle: new failure (last pass: v4.19.113-79-g81a370c0d238)
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-03-31 16:04 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=5e8369f9.1c69fb81.5fe9b.8cc5@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.