From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org
Subject: stable-rc/linux-5.6.y boot: 143 boots: 3 failed, 132 passed with 4 offline, 4 untried/unknown (v5.6.7-164-g86cfba65ced0)
Date: Tue, 28 Apr 2020 00:56:31 -0700 (PDT) [thread overview]
Message-ID: <5ea7e1af.1c69fb81.f92e5.dc3f@mx.google.com> (raw)
stable-rc/linux-5.6.y boot: 143 boots: 3 failed, 132 passed with 4 offline, 4 untried/unknown (v5.6.7-164-g86cfba65ced0)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.6.y/kernel/v5.6.7-164-g86cfba65ced0/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-5.6.y/kernel/v5.6.7-164-g86cfba65ced0/
Tree: stable-rc
Branch: linux-5.6.y
Git Describe: v5.6.7-164-g86cfba65ced0
Git Commit: 86cfba65ced0c2c8bdc2fc919361cc85f1c3ff67
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 96 unique boards, 24 SoC families, 22 builds out of 200
Boot Regressions Detected:
arm:
sunxi_defconfig:
gcc-8:
sun4i-a10-olinuxino-lime:
lab-baylibre: new failure (last pass: v5.6.7)
arm64:
defconfig:
gcc-8:
meson-axg-s400:
lab-baylibre-seattle: new failure (last pass: v5.6.7)
sun50i-a64-pine64-plus:
lab-baylibre: new failure (last pass: v5.6.7)
i386:
i386_defconfig:
gcc-8:
qemu_i386:
lab-baylibre: new failure (last pass: v5.6.7)
Boot Failures Detected:
i386:
i386_defconfig:
gcc-8:
qemu_i386: 1 failed lab
arm64:
defconfig:
gcc-8:
sun50i-a64-pine64-plus: 1 failed lab
arm:
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained: 1 failed lab
Offline Platforms:
arm64:
defconfig:
gcc-8
meson-axg-s400: 1 offline lab
arm:
multi_v7_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
stih410-b2120: 1 offline lab
qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-04-28 7:56 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=5ea7e1af.1c69fb81.f92e5.dc3f@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.