From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org
Subject: stable-rc/linux-5.6.y boot: 94 boots: 4 failed, 84 passed with 3 offline, 3 untried/unknown (v5.6.6-39-gc5f3b541dbc1)
Date: Tue, 21 Apr 2020 22:27:53 -0700 (PDT) [thread overview]
Message-ID: <5e9fd5d9.1c69fb81.25e3e.a0bb@mx.google.com> (raw)
stable-rc/linux-5.6.y boot: 94 boots: 4 failed, 84 passed with 3 offline, 3 untried/unknown (v5.6.6-39-gc5f3b541dbc1)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.6.y/kernel/v5.6.6-39-gc5f3b541dbc1/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-5.6.y/kernel/v5.6.6-39-gc5f3b541dbc1/
Tree: stable-rc
Branch: linux-5.6.y
Git Describe: v5.6.6-39-gc5f3b541dbc1
Git Commit: c5f3b541dbc18fab0209e9a184f9f6db5056bf37
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 64 unique boards, 20 SoC families, 19 builds out of 200
Boot Regressions Detected:
arm:
exynos_defconfig:
gcc-8:
exynos5422-odroidxu3:
lab-collabora: new failure (last pass: v5.6.6)
multi_v7_defconfig:
gcc-8:
sun8i-a83t-bananapi-m3:
lab-clabbe: new failure (last pass: v5.6.6)
arm64:
defconfig:
gcc-8:
meson-axg-s400:
lab-baylibre-seattle: new failure (last pass: v5.6.5-72-g906ecc0031ed)
i386:
i386_defconfig:
gcc-8:
qemu_i386:
lab-collabora: new failure (last pass: v5.6.6)
Boot Failures Detected:
arm:
exynos_defconfig:
gcc-8:
exynos5422-odroidxu3: 1 failed lab
multi_v7_defconfig:
gcc-8:
bcm2836-rpi-2-b: 1 failed lab
stih410-b2120: 1 failed lab
i386:
i386_defconfig:
gcc-8:
qemu_i386: 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-22 5:27 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=5e9fd5d9.1c69fb81.25e3e.a0bb@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.