From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org
Subject: stable-rc/linux-5.6.y boot: 164 boots: 3 failed, 148 passed with 7 offline, 6 untried/unknown (v5.6.2-30-g14d42f1aa3c3)
Date: Tue, 07 Apr 2020 14:51:10 -0700 (PDT) [thread overview]
Message-ID: <5e8cf5ce.1c69fb81.f96ac.a669@mx.google.com> (raw)
stable-rc/linux-5.6.y boot: 164 boots: 3 failed, 148 passed with 7 offline, 6 untried/unknown (v5.6.2-30-g14d42f1aa3c3)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.6.y/kernel/v5.6.2-30-g14d42f1aa3c3/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-5.6.y/kernel/v5.6.2-30-g14d42f1aa3c3/
Tree: stable-rc
Branch: linux-5.6.y
Git Describe: v5.6.2-30-g14d42f1aa3c3
Git Commit: 14d42f1aa3c34cb80141366c231981dff6cdc7cd
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 102 unique boards, 24 SoC families, 20 builds out of 200
Boot Regressions Detected:
arm64:
defconfig:
gcc-8:
meson-axg-s400:
lab-baylibre-seattle: new failure (last pass: v5.6.2-29-g99950f10b1ac)
meson-gxl-s805x-p241:
lab-baylibre: new failure (last pass: v5.6.2-29-g99950f10b1ac)
Boot Failures Detected:
arm:
multi_v7_defconfig:
gcc-8:
bcm2836-rpi-2-b: 1 failed lab
exynos_defconfig:
gcc-8:
exynos5422-odroidxu3: 1 failed lab
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained: 1 failed lab
Offline Platforms:
arm:
davinci_all_defconfig:
gcc-8
da850-evm: 1 offline lab
qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
multi_v7_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
qcom-apq8064-cm-qs600: 1 offline lab
stih410-b2120: 1 offline lab
exynos_defconfig:
gcc-8
exynos5800-peach-pi: 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-07 21:51 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=5e8cf5ce.1c69fb81.f96ac.a669@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.